Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snapshot Tool #16

Closed
mvandeberg opened this issue Dec 11, 2017 · 2 comments
Closed

Snapshot Tool #16

mvandeberg opened this issue Dec 11, 2017 · 2 comments

Comments

@mvandeberg
Copy link

mvandeberg commented Dec 11, 2017

The snapshot tool needs to capture existing accounts and witnesses.

From the accounts, the only fields we care about are:

name
json_metadata
posting
memo_key

For witnesses, the only fields we care about are:

owner

Other field are either populated by the blockchain, or will be replaced during conversion to the testnet.

The script also needs a list of the top 30 witnesses. While we only need 21 for block production, we will vote for 30 because that is the maximum number of witness votes allowed and will maximize the number of witnesses that can easily participate in the test net.

The output of this should be an array of accounts and an array of witnesses, either as a JSON formatted string, or in the native array/object format of the scripting environment.

@theoreticalbts
Copy link
Contributor

The tinman snapshot command's purpose is to create a JSON blob of all the information from mainnet that goes into creating the testnet's fastgen transactions.

Currently tinman snapshot includes all account data returned by the API for all accounts, and DGPO.

What you're suggesting is that tinman snapshot also include data about the witnesses, and filter some of the unneeded data from accounts.

IMHO filtering fields is a non-goal right now. It doesn't matter if the snapshot's a little bigger than it needs to be, it will probably never escape the machine it's generated on.

So I'd say just have tinman snapshot dump all the witness data as well and let txgen decide what it does / doesn't want.

Also, this might be different depending on whether you want a type (a) or type (b) testnet #22.

@theoreticalbts
Copy link
Contributor

To clarify, the only thing that needs to be done for this ticket is witness data needs to be added to tinman snapshot.

mvandeberg pushed a commit that referenced this issue Dec 29, 2017
Issue #16 Snapshot tool extended by wintness info dump.
@vogel76 vogel76 closed this as completed Jan 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants