Everything we get
asked

Nothing. The design has no protocol fee, no cut of trading fees and no allocation of any coin launched here. The vault program is meant to ship with no admin and a revoked upgrade authority, so nobody could add a fee later.

No. The slab stays with its holder or custodian, and nothing on Solana can hold it. What goes on chain is the pairing: which certificate this coin refers to, written so it cannot be changed. Treat it as a verifiable claim about identity, not as collateral.

There is no setter. The grader, certificate and card name are written into a program-derived account in the transaction that binds the coin, and no instruction can rewrite them. A second bind against the same certificate is refused outright.

The vault is designed with no team instruction: no admin, no withdraw, no upgrade authority. Every path out of it leads to a token burn. The realistic failure mode is not a rug pull, it is a bug, and unaudited code has bugs more often than anyone admits.

They buy the coin on its own pool and the tokens are burned. Anyone can trigger it by calling recycle, and the caller earns nothing for doing so. Supply only ever falls.

One certificate, one coin. The certificate record is a PDA seeded by grader and certificate number, so the second bind fails because the account already exists, even with a different name.

The pairing is keyed to the mint the launch will create from the name, ticker and creator wallet. Launch with any of those different and you get a coin the vault has no binding for, and recycle will refuse it. Bind first, then launch with exactly those values.

Anyone. Recycle is permissionless and pays the caller nothing, so it happens when somebody who wants the supply to fall spends the transaction fee.

Neither yet. The Solana program is not deployed and nothing here has been audited. Nothing here is a security or an investment product, and nothing on this site is advice. Read the program once it is published, then decide.