Usage, counted apart

All time, with the last 7 days in grey

Updated 2026-11-13 03:45 UTC. Refreshed at most hourly while people view this page, and once a day on a schedule.

How each number is counted

• Team vaults, external owners and Canary participants are counted apart. A vault is team when we run it, and external when its owner registered it themselves. Canary participants are people who tried the public Canary and are not on the team.
• Canary participants come only from Canary attempts by people who are not on the team. A team member's Canary attempts are counted under team. The Canary's own vault is left out of every figure taken from a ledger, so an attempt is not counted twice.
• In the Canary column, vaults, mandates, payments and held spends are the Canary vault's own on-chain events. Refusals, attempts and model decisions come from the attempts instead, because the Canary's ledger is private.
• These are counts, not dollar volumes. Amounts are not added up, so nothing here comes from the team paying itself.
• External owners: the distinct owner wallets of external vaults on this network.
• Canary participants: shown as at least that many people. It is the smaller of the distinct browsers and the distinct network addresses of people who are not on the team.
• Vaults: a vault counts on the day it was registered.
• Payments and mandates come from on-chain events our watcher records. Payments made includes the cross-chain payouts to Base, which are also shown on their own row.
• Held for approval: a spend the contract held for a human approver.
• Refused by code: for a vault, a decision in its signed ledger with the verdict refuse. For the Canary, an attempt that the code rules refused.
• Refused on chain: a spend the contract refused, with its transaction. A spend that a dry run stops before it is sent has no transaction and is not counted here.
• Canary attempts: every attempt that was recorded. One that did not finish is counted as an attempt and nothing else, once 90 seconds have passed. Sent straight to the contract means a code-refused attempt that was also sent on chain, bypassing the code rules.
• Model decisions: decisions where a model gave an answer. For a vault, a ledger decision that carries attestation evidence. For the Canary, an attempt with a model answer.
• Tokens per decision: the tokens the model reported, divided by its decisions, for the same segment.
• This page counts NEAR testnet only, with test tokens. Activity on the other NEAR network is counted apart and is not added in.
• Pilots are counted by cohort from our pilot list, and are not split by network. A pilot's name appears only with its written consent.
• Days are UTC. A day is computed while it runs and once more early the next day, and the totals add up the days computed so far.