$ARCH
An ERC-20 token on Robinhood Chain whose supply only shrinks and whose backing only grows. Every ARCH is a proportional claim on the Vault that you — not a committee, not a redemption window — decide when to execute.
The token, in numbers.
| Name | ARCH |
| Ticker | $ARCH |
| Chain | Robinhood Chain |
| Standard | ERC-20 |
| Initial supply | 1,000,000,000 |
| Owner | None — never written |
| Mint function | None — supply is fixed |
| Supply direction | Down only |
Where it lives.
TBATBAAddresses publish here and on @usearch_ at the same moment. Anything circulating before that is not ours — verify against this page before you touch it.
One direction.
Two forces remove ARCH from existence — the Buttress buying and burning during crashes, and holders burning to claim. Nothing puts any back.
Circulating supply is read from the contract on Robinhood Chain. The bar only ever moves right — there is no mint function.
What people actually ask.
What does holding ARCH entitle me to?
A proportional claim on the Vault, executable by you at any time. Burn your ARCH and the program pays out V × B / S in ETH, minus a fixed 1% that stays inside for everyone who remains. It is not a dividend and not a request — it is an instruction you call.
Does the team hold a treasury allocation?
The team's share is defined in the routing rule — 5% of revenue, taken automatically as it arrives. It is named up front and it cannot reach either pot. There is no separate discretionary pile that gets 'managed'.
Can the backing per ARCH go down?
Not through the mechanism. Revenue only adds ETH, the Buttress only removes supply, and claim fees stay inside. Market price is a different thing entirely and can trade anywhere — below backing or far above it.
What happens if nobody trades?
Backing stops growing, because backing grows only as fast as real revenue arrives. Nothing breaks and nothing leaks; the Vault simply stays where it is and remains claimable.
Can the rules change after launch?
Parameters like shot size and cooldown sit behind a 24-hour public timelock, so any change is visible on-chain a full day before it can execute. The four core promises are not parameters and cannot be changed at all.