docs · 07
The Revive Vault
Each requested coin gets a Revive Vault address. If pump.fun approves a CTO, the ask is that admin_cto sets the creator to that address. Creator fees would then land on a wallet the original dev does not control, and a program would pay diamond hands from it. That is the trust model: no team multisig sitting on the fees, and no "trust us, we will forward them."
What exists today
The address is a placeholder. It is a public key derived from the mint string. It is not a deployed program. It cannot custody fees, and it cannot pay holders. Do not send SOL or tokens to it.
On-chain versus off-chain
- On-chain when setup succeeded: the devnet $UNDEAD mint, fee transfers to the treasury, burns, refunds, the faucet, and stake transfers into a stake vault keypair.
- Market reads: Dexscreener and the pump.fun coin page, for the three health-check rows. Mainnet writes are refused.
- Signed messages: support, votes, and mock payments use ed25519. The signature is checked. A mock payment is not a transfer.
- Off-chain: the request ledger, vote tally storage, holder snapshots, dossiers, and the decision to email pump.fun. Without Upstash, that ledger is a local file, or memory plus /tmp on one serverless instance.
- Not on-chain: the Revive Vault program, creator-fee sweep, anti-bundle indexer, admin_cto watcher, and any SOL payout.