MONARKFleetNarabiUkemiBellit abstains so DeFi can act.
Dōjō
upcoming

Dōjō · hold snapshot

A dated, public record of the MONARK token balances held by each address, read from the chain through two distinct operators, with a hold score per address. Every line is published, signed and chained, and anyone can recompute it.

Latest snapshot: 2026-10-02 UTC · 4 of 4 scheduled readings between slots 452463776 and 452686880 · 288 lines · Merkle root f74af5f32e1f5b2cfcfea0e58a03b551ff74854b8a190251e98f68961b2d1822

These figures were committed with this page. A browser that runs its script and can check Ed25519 signatures then rereads the published timeline and lines file, and replaces these figures only when every check holds.

Total hold score: 8728988561.030649 · validated: 0.000000

A browser that runs its script lists here the lines of the snapshot shown above, once the lines file's SHA-256, count and Merkle root match the signed line.

How it is counted

Tiers: Egg, Caterpillar, Chrysalis, Monarch, Migration, each a number of units; Egg is the first. No unit version is in force yet: the first one needs seven counted days with both daily series read on the chain, and until it applies no address holds a unit or a tier.

Each day, every address is read at instants drawn from a seed committed in advance and revealed afterwards; the day counts the smallest reading, and an account no longer found counts as zero. When a balance decreases, the part that left starts again from zero, newest first. The hold score is the sum, over the days counted, of the part still held. Points become validated once the part that produced them has been held for 30 days in a row, and stay provisional until then.

The days before the first day read, from the token's creation on, were rebuilt once from the token's transaction history, read through two distinct operators: each such day counts the smallest balance each address held that day, at the start of the day or after any of its transactions. They are published in the history file that a signed line of the timeline names by its SHA-256, and the first day read continues from them as from a previous day's line.

An address off the Ed25519 curve is a program address, such as a pool or an escrow, or an address no key can sign for: its line is published with the class program and a hold score of zero.

What a snapshot shows: the balances two distinct operators reported for each address at the recorded slots, and the hold score computed from them. What it does not show: that an address belongs to one person, the balance between two readings, or anything to come.

Check it yourself

Check it yourself: download the signed timeline and a day's lines file; its SHA-256 must equal the value the signed line carries. Rebuild the Merkle root from the lines, sorted by address. Recompute your line from the previous day's line and the day's readings, and the unit and the dust threshold from the anchor line's objective and the two daily series the version line publishes. Check the signature with the published key. The check does not read the chain.

The Merkle tree hashes each line with a leaf prefix and each pair with a node prefix, and splits at the largest power of two below the count.

The instants of a day also depend on the signature of a public randomness beacon, published with that day's snapshot; this page does not check that signature, and any client of that beacon can, with the key named in the anchor line.