ARCH
An arch gets stronger the harder you push on it. Every unit of revenue splits automatically into permanent ETH backing you can claim, ammunition that fires only when the market breaks, and supply that is destroyed for good. Nothing leaks back out, and the promises that matter are not parameters anyone can change.
A token that backs itself and defends itself.
This idea is not new. Doing it continuously is — and that only works on a chain fast and cheap enough to never stop. The rules live in immutable programs; adjustable parameters sit behind a 24-hour public timelock, and the core promises are not adjustable at all.
Backing you can execute
Backing that someone else controls is not backing — it is a balance sheet you are invited to look at. The Vault is a claim you execute yourself: burn your position, receive your proportional share of the ETH inside. Not a request. Not a redemption window. A function you call.
Ammunition, not a bid
A bid that is permanently parked is just a target — everyone knows where it sits, so it gets fed until it is empty. The Buttress watches continuously and commits conditionally: it fires only on real damage, scales with how far and how fast price fell, and burns every token it buys.
Nothing leaks out
Two pots that cannot reach each other, and neither can reach us. The Vault cannot fund the Buttress. The Buttress cannot pay the team. There is a small operations share defined in the same routing rule — named up front, taken automatically, unable to touch either pot.
One engine, three destinations.
Revenue arrives from trading fees on the ARCH venue, and anyone can top the machine up with ETH directly. Either way it 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.
Constant attention. Conditional commitment.
When the Buttress does commit, it scales with how far price fell and how violently it got there — and it is capped per shot and per day, because the job is surviving a long war, not emptying the magazine into the first red candle.
Even the automation that proposes a shot is untrusted: the program re-checks every rule on-chain before spending a single wei.
Not speed as a slogan. On an expensive chain, every defensive action costs real money to send, so responses have to be big and rare — and in a crash you are bidding for blockspace at the exact moment everyone else is too.
Here, acting rounds to zero. Same ammunition, far finer control: small, precise, well-timed increments instead of one swing and a prayer.
Every time the Buttress fires, it buys and destroys. Supply drops. The Vault does not.
Which means the backing behind every remaining unit is higher after the crash than before it. Most systems try to survive volatility. This one eats it.
The promises that cannot be changed.
Every adjustable parameter is owned by a 24-hour timelock — no change without a full day of public notice on-chain. The biggest promises are not parameters at all.
- 01Vault ETH can never fund the Buttress.
- 02Buttress ETH can never reach the team.
- 03Everything the Buttress buys must be burned.
- 04The claim formula is fixed forever.
The machine is code.
Read exactly what it does, in plain language, with every number named.