EMBER
Every trade feeds the fire.
10% on every buy. 10% on every sell. None of it goes to a wallet. It all falls into the Burn Vault, a contract with no exit that waits for someone to dump, buys their bag, and sets it on fire.
not launched yet
TEN PERCENT, BOTH WAYS.
Pons v2 lets a token carry one creator tax that hits buys and sells the same. The factory caps it at 1000 bps. EMBER is set at the cap, so it is the hottest a Pons token is allowed to burn, and nobody can ever turn it up further.
Buy or sell, same fire
One rate for both directions. There is no sneaky asymmetry waiting for you on the way out.
Into the vault
Not a treasury. Not a marketing wallet. Not a multisig. A contract whose only outbound call is a buyback.
Minted once, never again
One billion, straight from the Pons factory. No mint function exists, so the only supply event left is a burn.
IT EATS SELL PRESSURE.
Most tax tokens sit on the money and burn on a schedule, which is the same as burning at random. The Burn Vault does the opposite. It sits quietly with a tank of fuel and waits. When a real sell hits the curve, it fires back in the same breath, buys what was dumped, and sends it to the dead address in the very same transaction.
Sell pressure
Rolling window of net sells on the curve. Cross the threshold and the vault is armed to answer it.
Drawdown
Price down a set percent from the rolling high. Red candles are literally what the fuel is for.
Full tank
Fuel has to clear a minimum before a burn can fire, so the vault never wastes half its ticket on gas.
Cooldown
A floor on blocks between burns. You cannot farm the vault by slicing one dump into a hundred pieces.
It sizes the bid to the dump
A tiny sell gets a tiny answer. A whale exit gets hit with everything the vault can responsibly spend. It never empties the tank in one shot, because the next dump also deserves a welcome.
There is no exit
This is the part that actually matters. The vault has exactly one function that moves value, and it moves it into a buy on the EMBER curve. There is no withdraw, no sweep, no owner transfer, no upgrade proxy, no admin key that can point the fuel somewhere else.
Tokens it buys are never held. They go to the dead address inside the same transaction that bought them, so there is not even a block of time where the vault holds a bag it could be talked into selling.
Anyone can pull the trigger. ignite()
is permissionless. If our keeper vanishes tomorrow, the vault still works. Anybody can fire it the moment
the conditions are true, and the gas refund goes to whoever bothered.
spend = min( fuel × maxBurnBps, // never all at once sellSize × matchBps, // sized to the dump fuel − reserve // keep powder dry) tokensOut = curve.buy{value: spend}(spend, minOut, vault)burn(tokensOut) → 0x…dEaD // same tx, always
FAST ENOUGH TO ANSWER.
A buyback that shows up four minutes after the dump is a press release. The whole point of the vault is being early enough to matter, which is a latency problem before it is a tokenomics problem.
Goldsky stream
The keeper does not poll a public RPC and hope. It sits on a dedicated Goldsky endpoint and gets curve swap events pushed the moment they land, which is how the vault can react inside the next block instead of the next minute.
Triggers off chain, truth on chain
The keeper decides when to call. The vault decides whether that call is allowed. Every trigger is re-checked in the contract, so a keeper that is wrong, greedy or compromised simply gets reverted.
One atomic transaction
Claim, buy, burn. Three steps, one transaction, no intermediate state anyone can sandwich or interrupt. If any leg fails, the whole thing reverts and the fuel stays exactly where it was.
Built on what Pons actually does
Not on what the docs claim. Every line below was confirmed by simulating real calls against a live Pons v2 curve on Robinhood Chain, before a line of the vault was written.
curve.buy(uint256 amountIn, uint256 minOut, address to)
payable, and it reverts unless amountIn equals msg.value. Getting this wrong is a silent failure.escrow.claim()
pays the caller's accrued creator tax out in native ETHcurve.sweepFees(uint256)
pushes what the curve is holding into the escrow first, so nothing is left behindmaxCreatorTaxBps() == 1000
the factory ceiling. EMBER sits on it, so the tax can never be raised on you.And the vault is the fee recipient, set at launch, so the 10% never touches a human hand at any point on its way to the fire.
Tax lands
Pons credits the creator tax to the fee recipient. That is the vault contract, not a wallet, and it is fixed at launch.
▶Untaxed on the way in
Pons exempts the fee recipient from its own tax, so every wei of fuel becomes EMBER instead of 10% of it looping back round into the escrow.
▶Nobody can re-point it
Because the fee wallet is a contract with no owner, nobody gets to swap it for a fresh EOA six weeks in. That is usually how these stories end.
GONE FOREVER.
Read straight off Robinhood Chain: how much EMBER is sitting in the dead address right now, against the one billion that ever existed.
1,000,000,000
Everything that still exists, which is total supply minus the dead address.
0x000000000000000000000000000000000000dEaD
Nobody has the keys. Nobody ever did. What lands here is out of the game permanently.
Go look yourself
Every claim, every buyback and every burn is a public transaction on the explorer. Do not take our word for any of it.
THE SHORT VERSION.
So the tax really is 10% both ways?
Yes, and it cannot go higher. Pons v2 applies a single creator tax rate to buys and sells, and the factory caps it at 1000 bps. EMBER launches at the cap. Add the standard 1% Pons curve fee and you pay 11% per side, so set your slippage above 11% or the trade will bounce.
Why a vault instead of just a wallet doing buybacks?
Because a wallet is a promise and a contract is a rule. A wallet can change its mind, get drained, get bored or get greedy. The vault physically cannot send the fuel anywhere except into buying EMBER, and it cannot hold what it buys.
What stops the team draining it?
There is no function to drain. No withdraw, no sweep, no rescue, no owner transfer, no upgrade path. The only thing anybody can do to the vault is tell it to buy and burn, and even that is gated by the triggers.
What if your keeper goes down?
Nothing breaks. ignite() is permissionless, so any bot or any person can fire the vault the second the on-chain conditions are met. The keeper is an optimisation, not a dependency.
Can it be sandwiched or MEV'd?
The buy carries a minOut computed from an on-chain quote, and the spend is capped per call and per window. A sandwich that pushes the price past minOut just makes the transaction revert, and the fuel stays in the tank.
How do I actually buy?
Robinhood Chain, on the Pons page for EMBER, using the contract address up top. Slippage above 11%. Do not buy more than you would shrug at losing.