Reproducing the Snapshot
Auditing the Snapshot is simply reproducing a snapshot directly from blockchain data and comparing it with the officially published snapshot data.
Getting the Registration Deadline slot number
Getting the slot_no
aligned with the registration deadline.
Query the dbSync database with:
The result will be:
Therefore the slot#
that the snapshot needs to target is: 140572806
Running the Raw snapshot
The first part of the snapshot accumulates raw registration and staked ada information and validates it according to CIP-15 and CIP-36.
Note: Multiple delegations, as specified by CIP-36, are not supported. These will be detected as invalid registrations. Only registrations that contain a single voting key are supported and valid.
Run (replace your credentials as appropriate):
This will produce three files:
cexplorer-140572806.json
<- Raw Snapshot Datacexplorer-140572806.unregistered.json
<- Unregistered but staked ADA.cexplorer-140572806.errors.json
<- Errors or Obsolete registrations.
Processing the snapshot with Fund 11 parameters
This filters registrations for minimum allowed voting power:
Run:
This produces the final snapshot: cexplorer-140572806.summary.json
Official Snapshot Artifacts
As soon as the official snapshot artifacts that will be used for Fund 13 are available, they will be linked to here.
It is possible to run the snapshot independently until they are published.
Last updated