How the light is counted
What a sigil is
Every wallet is issued exactly one sigil per UTC day. Pressing it means signing a message over a nonce this server issued to that address for that day; the server checks the signature recovers to the same address, spends the nonce, and writes the sigil into the record. No second sigil is issued to a wallet until the day is sealed at 00:00 UTC. It costs no gas, moves no funds, touches no contract and grants no approval — the signature is kept exactly as it was signed, and can be checked against the wallet that made it.
The people's leaf is built only from sigils offered, and is never weighted by what a wallet holds. That is the whole point: a leaf of deposits can be bought with size, and this one cannot. It can be bought with wallets, which is why every rank prints the number of wallets standing behind it.
Where the deposits come from
From DefiLlama, and nowhere else. Two keyless endpoints are read on a schedule: api.llama.fi/protocols, filtered to the protocols reporting TVL on this chain, and api.llama.fi/v2/chains for the chain total beside them. Every rebuild is stored with the second it was read, and every rank on this site is only true as of that moment.
Last successful read: 2026-09-10 04:12:11 UTC. Plinths carried: 146. Chain total as reported: $891.57M.
The deposits leaf is not additive. A risk curator and the lending market beneath it both report the same deposits, so adding the rows can exceed the chain's own total. This site prints whose number each row is and when it was read, and never sums them.
This chain's block explorer is deliberately not a dependency. On 2026-09-09 its API answered a Cloudflare interstitial rather than JSON, so there is no holder count anywhere here and nothing on this site implies an on-chain measurement.
What a sealed day is
At 00:00 UTC the day is sealed in wax. Both leaves are frozen into the record exactly as they stood, and a sealed day is never edited afterwards. If the deposits could not be read for a day, that day is published incomplete — never as a day whose numbers were zero. The record is on sealed days.
The two things this measures
- That the ritual is honest: one sigil per wallet per day enforced by signature and nonce, days sealed at a fixed hour and never edited, the read time shown on every rebuild, and a failed read published as incomplete.
- The size and persistence of the rank gap: how many plinths sit five or more places apart between the two leaves, and whether a plinth the faithful lit early later climbs the deposits' leaf. The second number is the one worth having and the one most likely to come out empty.
How this fails
- A wallet is not a person. One hand can press sigils from many wallets. Every count here is a count of wallets and says so; it is not a count of people and must never be read as one.
- The leaves may converge. If after several sealed weeks the two leaves agree at almost every rank, the sigils add nothing and this is a slower DefiLlama. The counter on the ledger is where that shows.
- The gap may be farming. A rank that moves only through bursts of new wallets lighting one plinth is not devotion. Wallet counts and first-seen dates are published so that is visible rather than hidden.
- A high place is not an endorsement. It is attention, measured. It is never a claim that a plinth is safe, audited, or worth depositing into, and nothing here is financial advice.
Reading the record as data
/api/v1/orders?side=gap — the distance between the two leaves. side is money, people or gap; page and limit page it, fifty rows at most, the same ceiling the pages use. The response carries the read time and the not-additive note with every page.