Proof, not promises

PopLocker has no withdraw, transfer, or arbitrary-call function. Read the verified source. Every graduated position NFT is minted directly to it.

There is no admin override of a launch's creator fee recipient anywhere in the code. Only the current recipient can transfer it. Lost keys mean lost future fees. That is the price of this guarantee, and we say it out loud.

Every launch snapshots its economics at creation; the hook's fee policy is a constructor immutable. The registry's re-pegs and the owner's config changes apply to future launches only, never to a launch already live.

Anyone can list any graduated Pons token whose permanently locked ETH liquidity clears the floor, proven on-chain against the verified Pons factories. There is no delist function; a quote that loses its backing simply stops hosting new launches, automatically.

Plain fixed-supply ERC-20: no owner, no mint, no blacklist, no pause, no transfer hooks. Anti-snipe protection is a decaying tax on the curve, not token-level control.

The crossing buy itself triggers graduation; both phases are permissionless and retryable; the pool seeds at the curve's terminal price with no swap and no oracle; donations to the curve are ignored by construction.

The four ownable contracts are owned directly by the protocol owner, a single key, and its changes take effect immediately with no delay. That is the weakest part of this deployment and we would rather say so than imply a timelock we did not deploy. What that owner can reach is narrow and worth reading literally: launch configs and the snipe-tax window for FUTURE launches, and two rescue paths for quote tokens that turn hostile after listing. Those rescues pay only fixed recipients, the launch's own creator and the protocol treasury, so there is no address the owner can name. The reserve rescue unlocks only after 14 days, during which anyone can still complete the graduation permissionlessly. It cannot touch locked liquidity, cannot redirect a creator's fees, and cannot change the terms of a launch that already exists.

Every contract is immutable once deployed. A v2 is a new deployment; v1 launches run forever on v1.