Bind it, launch it, burn it

01

You bind the certificate

You call bind with the grading company, the certificate number and the card as it reads on the label. That row is written once and there is no function anywhere in the contract that can rewrite it.

One coin per certificate. A second bind against the same cert is refused, so two launches cannot both claim the same slab. The pairing is keyed to the coin address the launch will mint, derived before the coin exists.

02

The coin launches on pons

You launch on pons v2 with the same name, symbol and wallet you bound with, and name the vault as the creator fee recipient. Image, metadata and the dev buy are all set there.

The name, symbol and wallet have to match the bind exactly. The address is derived from all three, so a mismatch produces a coin nobody bound and fees that route nowhere useful.

03

Trading pays the vault

Every buy and sell pays a creator fee. It accrues to the vault instead of to whoever launched the coin, and the vault has no function that pays anyone at all.

That contract has no owner, no admin, no upgrade path and no withdraw. ETH can arrive; the only way out is through the router, buying the coin.

04

Anyone burns the supply

Anyone calls recycle. It sweeps the fees, buys the coin on its own pool and sends every token bought to the dead address. It is permissionless and pays the caller nothing, so it happens when somebody wants the supply to fall.

The part worth understanding before you buy: the card is not collateral. It lives on Polygon and nothing here holds it. What the contract guarantees is that the pairing cannot change and that fees can only ever burn supply.