The Snapshot

Aries Honorary Rules, A4:

The Snapshot is the Bitcoin block in which the transaction creating Aries Orbitals piece #3000 confirms. Standings at that block are final for track (a). Transactions in later blocks do not count.

Piece #3000 (2:102171) was created by transaction bef7ef5406a4015cdf4775152ba1e4f2df456a3d772e01141c4353b847d63f05, which confirmed in block 969566 (000000000000000000007622306b32aecaad9e95a5760ccfb22c0f6065769112) at position 255 of 2,448. Block 969566 is the Snapshot. The standings below are final for track (a) of A3: the 300 addresses ranked highest.

The list of record

The list of record is standings-final-969566.json. Its sha256 — the hash of record — is:

6de4c0254d80253926edbfe32e48a03e1f18a92a85c4f0fe94fc3ab6456bed46

1,261 addresses are ranked: every address that donated to the Receiving Address at or before block 969566, under the counting rule in Terms Section 6, and held at least one Aries Orbitals piece at block 969566. Ties are broken under A5. The leaderboard on this site shows ranks and addresses; the files here also carry the totals, which are public on the Bitcoin chain.

Files

• standings-public-969566.json (126 KB) — the final standings — rank and address
• standings-final-969566.csv (183 KB) — the list of record as CSV — rank, address, total sats, pieces held at the Snapshot, the block and position at which each address first reached its final total
• standings-final-969566.json (356 KB) — the list of record (the file the hash of record is taken over)
• treasury-history-969566.json (3.2 MB) — every confirmed transaction in the Receiving Address’s history at or before the Snapshot, as read from two public explorers that agreed
• holdings-969566.json (1.8 MB) — the holder of each piece #0001–#3000 at the Snapshot, with how it was traced
• recompute.py (20 KB) — the script that recomputes the list from the two files above (Python 3, standard library only)
• facts-969566.json (4 KB) — the counts on this page
• SHA256SUMS (1 KB) — sha256 of every file above

Recompute it yourself

The list was computed twice, by two implementations written separately — one of them from the rule text alone — and they agreed on every address, rank, total and tie. To check it:

sha256sum -c SHA256SUMS
python3 recompute.py --history treasury-history-969566.json --holdings holdings-969566.json --out standings.json

standings.json carries the same rows as standings-final-969566.json. Without our files, recompute.py --fetch --host https://mempool.space/api --treasury bc1pn2uzkwqjy5wtj44ncqkgwjnlhypglms46l4n8chudyj9jxdkmywsxa6k7w --snapshot-height 969566 --holdings holdings-969566.json --out standings.json reads the Receiving Address's history from a public explorer itself (paced, about one request every 1.5 seconds).

What else the Snapshot settled

• Mints refused because the round had minted out: 1 in block 969566 after piece #3000 (3,000 sats), and 41 in later blocks (123,781 sats). Under Terms 6.2 a refused mint is a donation; the ones in block 969566 count toward the standings, and the ones in later blocks do not (A4).
• Pieces destroyed by an ordinary (non-protocol) spend at or before block 969566: 0. A destroyed piece is held by no address.

Disputes

Disputes are open for 72 hours from this page's publication: from 2026-10-02 19:36 UTC until 2026-10-05 19:36 UTC. Raise one in the builders group (t.me/+Ld4JmrPXPNI5ZDEx) or with @OpenOrbiting on X, naming the address and the transaction. After the window the list is sealed and the Honorary round proceeds.