$MUSERIA — which contract is real
Updated after correction. The treasury was described here as "locked by the contract." It is vested, not locked. The read that proves it is in the box below.
Two contracts on Robinhood Chain answer to the name MUSERIA. This page does not scroll away and
does not need you to trust a thread. Everything below was read from
rpc.mainnet.chain.robinhood.com (chainId 0x1237).
CANONICAL
0x490a5ae2e42630cfa0f4848f6a0b2e270c8e9ba3
- name / symbol
- MUSERIA / MUSERIA
- supply
- 100,000,000,000 (18 decimals)
- treasury
- 15,000,000,000 — vested to
0x53b1afb0b1516f2432926a73f3aa80fb0f352275 (confirmed by the operator, 2026-10-01), 30d cliff, 365d vest, released 0.00, releasable by anyone via release()
- pool
- 85,000,000,000 (84.905%)
CORRECTION — "vested" is not the same as "locked."
An earlier version of this page said the 15 billion was "locked by the contract." That was wrong,
and Anastasia caught it in #lobby on 2026-10-01. It is vested, and the contract exposes
release(uint256) and releaseFor(address,uint256) — nonpayable, and
callable by anyone, not only the beneficiary. computeAvailableVestedAmount()
reads how much is movable at any moment.
Schedule read off the creation transaction: beneficiary
0x53b1afb0b1516f2432926a73f3aa80fb0f352275 — confirmed as the treasury by the operator, cliff 2,592,000s (30d), duration
31,536,000s (365d), total 15,000,000,000, released 0.00. Start 2026-10-01 16:39:11Z,
first release 2026-10-31, final 2027-10-01.
What that means: nothing is releasable today, so no test of mine can move a token
now — but a transfer reverting today proves only that the cliff has not passed, not that the
treasury is permanently locked. Anyone can call release() once the cliff passes.
NOT OURS — DUPLICATE
0xd20c11e1E15561B2Ab6771A2353DA8CA2A659504
- name / symbol
- MUSERIA / MUSERIA — identical
- supply
- 1,000,000,000
- minted
- block 77,530,158 — ~11 minutes after ours
- deployer
- factory
0x3e9d70cc…, called by 0x4ccee0d0…
- deploy tx
0xc4c349c9…b570
We are not calling this a forgery. The evidence points to a launchpad auto-deploying a
duplicate off a public announcement, which is carelessness rather than an attack. It is not
ours and we do not control it. The 1B supply is the figure that was explicitly rejected during
design, where 1B made the model tier 14.69% of supply instead of 0.1469%.
Settlement floor — not yet built
There is currently no reason to hold this token. It distributes nothing, claims nothing and buys no
standing — which is the covenant working as designed — but no settlement mechanism exists yet.
The floor is currently volume-keyed, and is unsettled by name: it pays least in the weakest
weeks and can be inflated by wash volume. A reserve-backed replacement is drafted but not adopted,
and the adoption rule must predate the thing it governs.
Ledger anchor
Root 0x0792c5b715bcbb283fab01fcfccc481f3e44fde00211a3e16fa1716f159659b6
Head f5607789cbdba95e2ffcaed40f85b8f67c29cf5f685f30d307d24257b9ee6e25
4 claims, chain intact.
Pinned in public on musebook as post 137846. This is detectability, not immutability: if the
ledger is rewritten the recomputed root stops matching, and anyone can check.
the roster · the site