Source and verification

Check a ranking in a few steps, or reconstruct every count from its exact archived inputs.

Reports, source and exact evidence are freely accessible without registration or payment.

Check a ranking

  1. On Report, select a window and read its covered interval, acquisition time and freshness.
  2. Download its complete CSV. It uses the same blocks as that view, including addresses outside the chart.
  3. Check that all row counts sum to the displayed eligible block total and the first 20 rows match the dashboard. Compare the selected file's SHA-256 below if checking exact bytes.
  4. Use Methodology for definitions and limitations, and the exact report source below to inspect the implementation.

These checks help compare outputs. Totals alone cannot prove every individual address count; the independent raw-header procedure below checks the complete distribution.

Complete CSV files and checksums

CSV manifest (SHA-256 3beec046ec3caf8241c7c09ec56234eca12bcd232bfd1cddfb0a87999613dc9b) binds all four files to this exact report. Immutable copies are in the same Registry report version.

Columns: Rank, Reward Address, Block Count, Percentage. UTF-8, comma-separated, RFC 4180 quoting and CRLF lines. Percentage uses all eligible blocks, with six decimal places and half-even rounding. Counts descend and tied addresses ascend; genesis is excluded. See the CSV guide.

Identify this exact snapshot

Immutable report version
r-20261106t120947-3036520202-17805508556
Acquired
Generated
Complete-day cutoff
Exact report source revision
d91603f6b74b299339499f57a84d2a3513861482
Exact identifiers, timestamps and report checksum
Release
0.1.0
Acquired / generated (UTC)
2026-11-06T12:10:12Z / 2026-11-06T12:10:18Z
Report SHA-256
ddb4d72e2a2a1d58817f1d5bc0adf5c8dd5eb12293ffa2f5623feda438a529e4
State version
s-20261106t120947-3036520202-17805508556-001
State manifest SHA-256
94b94c03a9291ede95dedf36e217ff420aff2fda3e6475e570b149ebd0b43e4f

Current report JSON · Exact Registry report · Complete evidence descriptor · Website release metadata

The descriptor identifies source, manifests, all raw partitions and CSV evidence with exact URLs, versions, sizes and SHA-256 values. The source revision belongs to the report; a documentation-only website revision can be newer without changing its historical data.

Independent reproduction for reviewers

  1. Record the report version, SHA-256 and exact source revision above. Check out that revision and prepare its pinned official-source decoder.
  2. Retrieve the committed report, state/prefix manifests and exact header partitions named by the descriptor. Verify their byte lengths and SHA-256 values.
  3. Reconstruct the recorded genesis-to-tip sequence; check official header IDs, heights, parent links, timestamps and archived coverage.
  4. Recompute all four R1.1 populations and rankings using the recorded generation instant and freshness policy.
  5. Regenerate complete CSVs and their manifest. Run the separate raw-offset/SQLite reconstruction to compare every address/count, boundary, percentage and Top 20.
  6. Compare the regenerated JSON, manifest and CSV bytes with the published snapshot.

The verifier implements this workflow. Provide Python 3.11+ and Go 1.26.2; its technical instructions specify source preparation and evidence retrieval.

Anonymous independent reproduction

Anyone can independently reproduce the published results using the available source code, report data, archived headers and verification tools. This procedure uses no account, token or browser session.

bash scripts/prepare-source.sh
PYTHONPATH=src python3 -m zbpo.verify r-20261106t120947-3036520202-17805508556 \
  --expected-sha256 ddb4d72e2a2a1d58817f1d5bc0adf5c8dd5eb12293ffa2f5623feda438a529e4 --out .state/new-reproduction

Reports remain historically reproducible after freshness expiry. A matching checksum binds recorded bytes, not full consensus validity. Count reproduction is separate from independent validation of proof of work, difficulty or chain selection; see validation levels.

Exact evidence and historical discovery

State manifest · Genesis-prefix manifest · Complete machine-readable descriptor

Raw header files and their checksums
  • Genesis prefix, heights 0–9,9992,600,000 bytes · version g-20261027t235235-2996834989-17522793787SHA-256 0e66cade098626ff2287657e93eebc2c320ac18b782385e7090e6e9165113275
  • Heights 10,000–24,9993,900,000 bytes · version c-90f567992d72ebcac4686e7ddcfbe52121adfe3e-20261104t120949-3026939770-17734073732-0SHA-256 90f567992d72ebcac4686e7ddcfbe52121adfe3ec67ad97cbd235b67657ed122
  • Heights 25,000–39,9993,900,000 bytes · version c-f723b3de9cd3b9be662c2ccaedd0f2eab9fc1acc-20261104t120949-3026939770-17734073732-1SHA-256 f723b3de9cd3b9be662c2ccaedd0f2eab9fc1accfc9b08a1dd18367940dff539
  • Heights 40,000–54,9993,900,000 bytes · version c-2b8a3458dd849191450b4f4a3e93acc963b6dc10-20261104t120949-3026939770-17734073732-2SHA-256 2b8a3458dd849191450b4f4a3e93acc963b6dc10bf5d0d66ca73943114bba3b0
  • Heights 55,000–69,9993,900,000 bytes · version c-5f668b92d43738d50d487cf6e2acfac20500eaf4-20261104t120949-3026939770-17734073732-3SHA-256 5f668b92d43738d50d487cf6e2acfac20500eaf4b0087990f8dc7fc9bbf68c5a
  • Heights 70,000–81,7863,064,620 bytes · version c-75e389e5a9d7a18b72b3e1b045d8b3c099c10fa40389a9c6b21597eadd748a9aSHA-256 75e389e5a9d7a18b72b3e1b045d8b3c099c10fa40389a9c6b21597eadd748a9a
  • Heights 81,787–82,15696,200 bytes · version s-20261104t120949-3026939770-17734073732-002SHA-256 23089cb1a5be61bc33ee7eeb3436305c3b82581f26952ff04734758cafd78173
  • Heights 82,157–85,023745,420 bytes · version s-20261105t121051-3031794939-17770207127-001SHA-256 5a664d70d588b58a25a473c5b29a2331881f25352a8a61cd048ec7aea5694089
  • Heights 85,024–87,897747,240 bytes · version s-20261106t120947-3036520202-17805508556-001SHA-256 37ceeca5f769e527e513703b10bd554d019f48f085adb7ff93b97cb0cd2c823e

Each production r-* package's commit.json embeds that report's descriptor. Use the Registry catalogue to discover historical versions and follow pagination. A committed report may precede a failed Pages deployment, so the current site's descriptor, not the newest catalogue entry alone, identifies what it serves.

Daily refreshes replace the current Pages files. Keep the immutable Registry version and checksums for historical citations; old Pages paths need not remain hosted. The original history is not deleted by compaction. Reproduction and CSV contract · Recovery runbook

Production source repository · MIT license · Third-party notices · Factual data policy