Skip to content

Latest commit

 

History

History
188 lines (133 loc) · 6.22 KB

SNAPSHOT-EXTRACT.md

File metadata and controls

188 lines (133 loc) · 6.22 KB
Raw

Snapshot data extraction

To extract the data, we need 2 snapshots, the one when the count happened to get the validators and delegations, and the one just before to get the votes (because votes are removed during the count). Let's call these files:

  • pre-tally-snaphost.json (just before the tally)
  • tally-snapshot.json (where the tally happened)

Pre-tally Block 18010657

This block is selected to be pre-tally for cosmoshub-4 proposal 848.

Download

An export is stored in S3 accessible here: https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/cosmoshub-4-export-18010657.json

How the block has been exported

On a stopped blockchain node containing the block 18010657:

$ gaiad export --height 18010657 > cosmoshub-4-export-18010657.json 2>&1

Verify the export

$ md5sum cosmoshub-4-export-18010657.json
84cdf83c11c7a88e0cf60070391a2519  cosmoshub-4-export-18010657.json

Note

The JSON schema of the export is the following : { "app_state" : { "gov": {...}, "staking": {...} } where each module object corresponds to the GenesisState proto message of the underlying module (example proto/cosmos/staking/v1beta1/genesis.proto for the staking module).

Tally Block 18010658

This block is selected to be tally for cosmoshub-4 proposal 848.

Download

An export is stored in S3 accessible here: https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/cosmoshub-4-export-18010658.json

On a stopped blockchain node containing the block 18010658:

$ gaiad export --height 18010658 > cosmoshub-4-export-18010658.json 2>&1

Verify the export

$ md5sum cosmoshub-4-export-18010658.json
7f34b4d2e2bce0f8b5308b396cfa1df4  cosmoshub-4-export-18010658.json

As mentioned earlier, this snapshot is used to extract validators, delegations, and the final votes that were submitted in that block.

Get direct & indirect voters

While direct voters are easy to extract, indirect voters must be determined by iterating over delegations and correlating them with validator votes.

Get all direct voters

$ jq '[.app_state.gov.votes[] | select(.proposal_id == "848")]' cosmoshub-4-export-18010657.json > votes.json

$ md5sum votes.json
a9782883000b3064e22d2200ea9cbdca  votes.json

Returns 173,165 votes (41Mb).

We need to manually add the final votes from block 18010658. There's only one and it's a vote that has already been broadcasted in block 17903222 with the same option (yes), so we can safely discard it.

The file is available here https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/prop848/votes.json

Tip

For documentation, here is an example command to add one of these final votes, in case you are extracting data for an other proposal:

$ jq '. += [{
  "option": "VOTE_OPTION_YES",
  "options": [
    {
      "option": "VOTE_OPTION_YES",
      "weight": "1.000000000000000000"
    }
  ],
  "proposal_id": "848",
  "voter": "cosmos1jq6rpkf233jq9h98tlarzk8w3pl3lx87sv3t28"
}]' votes.json > votes_final.json

If the final votes have duplicates, because the user has voted more than one time, we need to eliminate the first votes and keep only the last ones (maybe

Get all delegations

$ jq '.app_state.staking.delegations' cosmoshub-4-export-18010658.json > delegations.json

$ md5sum delegations.json
be316ecfb9d5853ffcb65b29cf1ddd8d  delegations.json

Returns 1,061,423 delegations (238Mb). If not found in direct voters, any delegation address will inherit validator's vote.

The file is available here https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/prop848/delegations.json

Get active bonded validators

$ jq '.app_state.staking.validators' cosmoshub-4-export-18010658.json > validators.json

$ md5sum validators.json
16cb26b14afb4799b5c2504285b2cc14  validators.json

Returns 531 validators (610Kb).

To have the active set, we need to:

  • Get the max_validator parameters:
$ jq '.app_state.staking.params.max_validators' cosmoshub-4-export-18010658.json
180
  • Filter out bonded validators
  • Sort by the tokens field (descending)
  • Limit to max_validators
$ jq '[.[] | select(.status == "BOND_STATUS_BONDED")] | sort_by(.tokens|tonumber) | reverse | .[:180]' validators.json > active_validators.json

$ md5sum active_validators.json
d3c09490eba24a1c0ec52fa9af3f28ac active_validators.json

Now we have only the 180 active validators.

This procedures follows the code of the staking.Keeper.IterateBondedValidatorsByPower() function, which is used in the x/gov.Keeper.Tally() function.

The file is available here https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/prop848/active_validators.json

Get proposal

The proposal is only used to verify the data.

jq '.app_state.gov.proposals[] | select(.proposal_id == "82") '  cosmoshub-4-export-18010658.json > prop.json

The file is available here https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/prop848/prop.json

Get balances

jq '.app_state.bank.balances' cosmoshub-4-export-18010658.json > balances.json

The file is available here https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/prop848/balances.json

Get account types

For the accounts command only, the auth genesis is required to add the Type of the account in the accounts.json file.

jq '.app_state.auth' cosmoshub-4-export-18010658.json > auth_genesis.json

The file is available here https://atomone.fra1.digitaloceanspaces.com/cosmoshub-4/prop848/auth_genesis.json