Burnhouse

Creator fees go in, the project's own token comes out and goes to 0x…dEaD. Permanently.

ETH burned0.000
Cycles run0
Projects0
Pons locks. Burnhouse burns. Pons has its own buyback switch, but the tokens it buys go into a vesting vault and the protocol keeps 30% on release — that is a lock, not a burn. A Burnhouse burner sends every token it buys to 0x…dEaD and cannot do anything else: no owner, no withdraw, no upgradeability. Anyone may call execute().
No burners deployed yet. Once a project points its Pons creator fees at a Burnhouse address, its burns appear here automatically — this page reads the contracts, not a database.

How a project connects

Compute the burner address with predict(), set it as the launch's creator-fee recipient on Pons, then deploy the burner with deploy(). Fees accrue in the Pons escrow from the first trade, so the address can be set before the contract exists.

A launch that already trades can hand over its fees with transferCreatorFeeRecipient() on the Pons factory — that works both on the bonding curve and after graduation.

Graduation is handled

Each execution reads the launch phase from Pons and routes the buy to the bonding curve or to the Uniswap v4 pool accordingly. The price anchor resets when the venue changes, because a pool's price is not comparable to a curve's — carrying it across would freeze the buyback.