Ponsvident

Ponsvident - fee engines for Pons. Point a launch's creatorFeeRecipient at an ownerless contract and its creator fees are spent by code, not promised by a wallet. No owner, no pause, no upgrade, no withdrawal function. ponsball promised buy-and-burn from a wallet in July 2026; its dead-address balance is still 0. Factory 0xA378B9CCAF530d0c81a265b734cF2cfF6321BB8c (chain 4663) POLICIES burn buys your token and delivers it to 0x...dEaD split pays a fixed set of addresses fixed shares, forever reflect pays holders who stake, per token per block HOW TO USE IT 1 a = factory.predictBurn(you, salt) -> your engine address, before it exists 2 launch on Pons naming a as creatorFeeRecipient, buybackEnabled false 3 factory.deployBurn(salt) -> lands exactly at a 4 engine.bind(token) -> only you, once, verified vs the factory 5 engine.poke(0) -> anyone, forever Already launched? transferCreatorFeeRecipient(token, a) then bind. After that no creator can take the stream back, including you. RULES WORTH KNOWING - buybackEnabled must be false. bind rejects it, and it can never be cleared afterwards, so such a launch could never sweep its own fees. - poke is rate-limited against the venue's own liquidity, so a permissionless poke cannot be sandwiched for the whole balance. - 5% of each claim is taken and held for PONSVIDENT holders. Distribution is announced publicly, not paid on chain. - Pons's owner can still redirect any launch's fees after a 3-day timelock. No engine can prevent that. Every engine publishes it: pendingRedirect(). - After graduation a pool buy leaves fees in the memecoin, which only Pons's operator can convert. Check sweepBlockedOnOperator(). Both quote assets work: native ETH and ERC-20 pair tokens. Not audited. Read the code before you point real fees at it.

Reading trades.