You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Example for building a newaccount transaction in eosjs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Telos work proposal #25 was opened with the target of implementing portable snapshots for Chronicle, so that Chronicle data can be easily moved between servers of different OS versions.
As of August 22nd, I added a new feature to Chronicle that allows starting it from a nodeos portable snapshot. So, there's no need to re-scan the whole history in order to get up to date Chronicle data. Now it's enough to point it to a node that just started from a snapshot. This eliminates the need for portable snapshots in Chronicle, so the initial purpose of the WP is obsoleted.
The work proposal asks for 50000 TLOS, which is approximately USD 2500 in current prices.
I propose to re-purpose the WP#25 and set the following deliverables:
@SirFuzzalot presented an idea for a new PB pay model for an EOSIO network in https://t.me/EOSPros
Fuzzy, [12.05.19 04:56]
Here is my thought on fixing dpos away from pageantry though.
Let me find the discussion (should prob post it on whaleshares first but oh well)
Fuzzy, [12.05.19 05:03]
Ok ill just type it here since i am no longer in the group i posted it in initially.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters