How the ascent is measured

What a claim is

Every wallet is issued exactly one claim per UTC day. Signing 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 claim into the record. No second claim is issued to a wallet until the wall locks 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 climbers' rope-wall is built only from claims signed, and is never weighted by what a wallet holds. That is the whole point: an altitude reading 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 behind it.

Where the altitude reading comes 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-13 09:12:04 UTC. Ropes carried: 154. Chain total as reported: $934.62M.

The altimeter reading 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 locked day is

At 00:00 UTC the wall locks and the beacon lights. Both pages are frozen into the record exactly as they stood, and a locked day is never edited afterwards. If the altimeter could not be read for a day, that day is published incomplete — never as a day whose numbers were zero. The record is on logged days.

The two things this measures

1. That the mechanism is honest: one claim per wallet per day enforced by signature and nonce, days locked at a fixed hour and never edited, the read time shown on every rebuild, and a failed read published as incomplete.
2. The size and persistence of the tension: how many ropes sit five or more places apart between the two readings, and whether a rope the climbers claimed early later climbs the altimeter's reading. 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 sign claims 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 two readings may converge. If after several locked weeks the two orders agree at almost every rank, the claims add nothing and this is a slower DefiLlama. The counter on the full rope-wall is where that shows.
• The tension may be wallet-farming. A rank that moves only through bursts of new wallets clipping one rope is not a real pull. 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 rope 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 readings. 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.