A token that defends itself and backs itself.
Revenue flows in. Most becomes claimable ETH backing. A large share becomes buy-and-burn firepower for crashes. Nobody presses a button, and the important rules cannot be changed at all.
The machine is code.
Introduction
ARCH is a meme token with a machine behind it. Every unit of revenue is split automatically between three destinations: a Vault of ETH any holder can claim against by burning ARCH, a Buttress that buys ARCH on the open market during real crashes and destroys what it buys, and the team. The rules live in immutable Robinhood Chain programs. Adjustable parameters sit behind a 24-hour public timelock; the core promises are not adjustable at all.
The entities
There are four moving parts. Everything in the system is a relationship between them.
| entity | what it is | tldr |
|---|---|---|
| $ARCH | The ERC-20 token | Burned by the Buttress and by claims. Supply only goes down. |
| The Vault | The ETH backing every ARCH | Leaves in exactly one way: a holder burns ARCH for their share. No admin key. |
| The Buttress | A pot of ETH with one legal move | Buys ARCH during 30%+ crashes, burns 100% of it. Cannot be withdrawn. |
| The Keystone | The allocation engine | Splits all incoming revenue 50 / 40 / 10. Anyone can trigger distribution. |
The revenue split
Revenue comes from ARCH's trading venue: creator fees earned on trading are routed straight to the machine, and anyone can top it up with ETH directly. Either way the money hits the same engine and splits 50 / 40 / 5 / 5 into Vault, Buttress, community and team.
Distribution is permissionless: once revenue accumulates, anyone can trigger the split. The team cannot sit on funds, and the ratios are enforced by the program, not by policy.
The Buttress
The Buttress is ETH with one legal move: buy ARCH during a serious drawdown and burn all of it. Burned tokens are permanently destroyed. There is no code path for anyone, including the team, to withdraw the Buttress's money.
When it fires. The Buttress compares price to Established Territory, a slow-moving reference built from time-averaged market data, so a single manipulated trade cannot move it. Below a 30% drawdown the Buttress starts firing, and it fires harder the deeper the crash, peaking around the 80–90% zone. Past 90% it deliberately eases off to preserve ammunition instead of emptying itself into a collapse.
Velocity. A crash in one hour is scarier than the same drop over a week. Fast drops can scale a shot up to at most 2×. Speed can never make the Buttress fire when the drawdown gate says no, and never breaks the caps below.
The caps exist so the Buttress survives long wars instead of blowing its budget on the first bad candle. Even the automation that proposes shots is untrusted: the program re-checks every rule on-chain before spending a single wei.
The Vault
The Vault holds the ETH that backs every circulating ARCH. Money leaves it in exactly one way: a holder burns ARCH and takes their proportional share. No admin key, no pause button, no borrowing by the Buttress. An emergency switch must never become a way to freeze or seize holder backing, so there is not one.
Backing per arch is the Vault's ETH divided by the redeemable supply. It is the floor amount one ARCH can always be exchanged for through the program, and three forces push it in one direction only:
Nothing in the mechanism can push the ratio down.
Burn & claim
Any holder can burn ARCH at any time for their share of the Vault. The formula is V × B / S: Vault balance, times ARCH burned, divided by redeemable supply.
- Vault balance · V
- —
- Circulating supply · S
- —
- You burn · B
- 5,000,000 ARCH
- Gross · V × B / S
- —
- Claim fee · 1% (stays in Vault)
- —
- You receive
- —
V and S come from the vault account and the mint. Neither exists yet, so the formula is shown without numbers rather than with invented ones.
The exchange is atomic: burn and payout happen in one transaction against the state right before your burn. The fee is fixed at deploy time and cannot be raised behind your back.
Guarded launch & timelock
Guarded launch. Young markets have thin liquidity, and a full-size Buttress shot into a thin pool would move price too much. So the Buttress starts with base shot and daily budget halved. Lifting guarded launch is one-way and goes through the timelock: the training wheels cannot come off silently, and can never be re-imposed to fake scarcity.
Timelock. Every adjustable parameter is owned by a 24-hour timelock. No parameter changes without a full day of public notice on-chain. And the biggest promises are not parameters at all:
- ▸Vault ETH can never fund the Buttress.
- ▸Buttress ETH can never reach the team.
- ▸Everything the Buttress buys must be burned.
- ▸The claim formula is fixed forever.
Honest risks
The Vault is a claimable backing mechanism, not a promise that market price cannot fall. Price is set by traders and can trade below, or far above, backing per arch. The Buttress softens crashes with real buy-and-burn pressure but is capped by design and cannot stop a determined market. Backing grows only as fast as real revenue arrives. And like all on-chain systems, the code can contain bugs despite careful design.
What the programs do guarantee is mechanics: your right to burn ARCH for your share of the Vault cannot be paused, frozen, or taken away by anyone.
Live on Robinhood Chain mainnet. Mint: 0xb7f55013a676ec4a691bf0d09bdb4a5baaefd70b. The Vault is a claimable backing mechanism, not a promise that market price cannot fall.