MusePass

Numbers

This page only carries things you can check. The name count comes from the chain's own events, so anyone can count it themselves; index numbers say where they come from; and what cannot be measured yet is listed below with the reason, rather than left out.

Names

Registered on chain (from the NameRegistered event)0
Distinct holder addresses on chain0
Rows in the index12 (database index)
Of those, cards published3
Waiting for certification to open0

Check it yourself: read the registrar's NameRegistered events, or run pnpm snapshot:names in this repository.

Invitations and the budget (first-500)

Sponsored registrations — the first long name of any wallet, or any name an invitation covers — are registered with gas the platform pays, so the giveaway is finite. These are the caps and how much of each is spent; when a cap is reached, claims pause and the claim endpoint says so. The invitation ledger publishes counts only: which wallets and accounts were invited is not published, on purpose.

Names issued (first-stage allocation)4 / 10000
Issued today / daily cap0 / 500
Estimated gas paid so far$0.04 / $200
Gas in the sponsor wallet0.00019 ETH
Invitations issued4
Spent on a 3–4 character name2
Still open2

One invitation covers one name; a 3–4 character short name spends it. The spend count comes from the database ledger.

Paid purchases

Short names and second names are sold for USDG, paid direct to a receive-only treasury address. Only completed purchases are counted here — a quote that expired or failed was never revenue, so it is not one.

Names bought1
Paid to the treasury$0.10 USDG
Last completed purchase2026-10-01 11:36 UTC

Registrations, last 14 days

Names registered per UTC day, from the same index as above — the same honesty label applies.

2026-11-012026-11-14

Coming back

A wallet counts as returning when it registered a second name or published a card within the window after its first name. Wallets younger than the window are not counted at all, and the counts are printed next to the share so a rate over three wallets cannot pretend to be a trend.

Returned within 1 day2 / 12 (17%)
Returned within 7 days3 / 12 (25%)

Not measurable yet

  • Who besides us has looked anything up: API and MCP calls are not counted per caller yet. Our own test runs would inflate the number, so we would rather report nothing than report that.
  • Records and verdicts: The record registry is written and tested but not deployed, so there is nothing on chain to read.
  • Records issued by a verifier outside our team: The only verifier today is our own engine. Calling that independent verification would be false.
  • Distinct users: A name maps to a wallet address, and one person can hold several. Counting addresses as people would be a guess.

For who can do what, and the risks, see the trust model. For what a batch of numbers can and cannot be made to say, see anchored batches.