Overview
RESPAWN is a pump.fun launch wrapper. A creator launches a normal pump.fun coin through RESPAWN and adds three things: declared dev wallets, a dev-sell pledge, and a respawn fund paid from creator fees. RESPAWN records the full holder list every few minutes.
If the declared wallets break the pledge, the RESPAWN keeper launches a v2 coin on pump.fun, spends the fund on its opening buy, and airdrops the v2 to everyone who held v1 in the last snapshot before the breach. The v1 page is marked RESPAWNED with a public breach report.
If the dev dumps, the community respawns. That is the promise, and the only one.
Rules
- Declared wallets: 1 to 5, including the creator wallet. Each signs a declaration message. Transfers between declared wallets are neutral.
- Dev bag = the v1 balance summed across declared wallets. High-water = the largest dev bag seen since launch.
- Outflow = any decrease of the dev bag: a sell to the curve or pool, or a transfer to any undeclared address.
- Breach when the outflow inside the rolling pledge window is more than the pledge share of high-water, or when the respawn vault is removed from or reduced in the coin's pump.fun fee-sharing config.
- Grace: the first 10 minutes after launch are not counted. Outflow during grace still lowers the high-water mark.
- The pledge can be tightened after launch, never loosened.
Pledge presets
| Preset | Max outflow | Rolling window |
|---|---|---|
| Diamond | 10% | 30 days |
| Standarddefault | 25% | 7 days |
| Builder | 50% | 30 days |
| Custom | 5–75% | 1–90 days |
Respawn fund
- A share of the coin's pump.fun creator fees goes to its respawn vault through pump.fun fee sharing. Default 50%, minimum 20%.
- Optional SOL bond from the creator, moved in the launch transaction.
- RESPAWN skims 10% of the vault's fee income as its protocol fee before it counts toward the fund. Launch fee on mainnet: 0.05 SOL.
- Fund cap 25 SOL. Above the cap, fee income goes back to the creator.
- A respawn needs at least 0.15 SOL. Below that, the coin goes to BREACHED_UNDERFUNDED: the breach report publishes, and the fund keeps accruing for 72 hours. If it reaches the minimum, the respawn proceeds against the same snapshot.
Snapshots
About every 3 minutes RESPAWN reads the full holder list of the coin, stores every row, and publishes a sha256 Merkle root. The breach snapshot is the latest snapshot taken before the slot of the outflow that pushed the dev over the limit. Anyone who bought after that slot is not in it.
Excluded: declared wallets, the bonding curve, the PumpSwap pool vault, program-owned accounts, the respawn vault, and balances below max(1,000 tokens, 0.0005% of supply).
Allocation
The v2 tokens bought are split pro rata to v1 balances in the breach snapshot. Each wallet is capped at 5% of the total; the excess is redistributed to uncapped holders. Rounding dust goes to the largest holder.
Push: the largest holders, as many as the fund can pay token-account rent for (max 500), receive tokens directly. Claim: everyone else signs a claim transaction, paying the fee and their own token-account rent. Unclaimed tokens stay in the vault after 30 days, shown publicly.
The v2 coin
Name: the v1 name plus "RESPAWNED". Ticker: the v1 ticker plus "2". Image: the v1 image with the respawn ring. It is a pump.fun Holder Rewards coin: creator fees go to v2 holders, never to a dev. The vault buys at creation and never sells.
The v2 is a new memecoin with no promised value.
Keeper & review mode
In this version respawns are executed by the RESPAWN keeper, an off-chain service that holds each coin's vault key (encrypted at rest, per-coin vaults, spend paths limited to respawn and airdrop instructions, fund cap 25 SOL, kill switch).
On mainnet, a detected breach becomes a respawn proposal that an operator approves or rejects (review mode). Pages show "pending keeper review" meanwhile. Every transaction is listed on the respawn page. The roadmap moves this to an on-chain program with posted snapshot roots and a permissionless crank.
What your wallet signs
RESPAWN only ever asks your wallet to sign four things, and explains each one before the prompt:
- Sign-in message (text starting "RESPAWN sign-in"). Not a transaction.
- Declaration message (text starting "RESPAWN declaration") for each declared wallet. Not a transaction.
- Launch transaction(s): create the coin, your dev buy, fee sharing with the vault, optional bond, memo.
- Claim transaction: moves your v2 allocation from the vault to you.
Risks & honest limits
- Undeclared wallets are not covered. A dev can sell from alts. Coin pages say so. Funding-cluster hints are on the roadmap, as information only.
- Keeper trust. Execution is off-chain in this version. Mitigations: public transaction log, review mode, snapshot hashes, open rules.
- Missed snapshots / RPC limits. Snapshots back off on rate limits. Breach reports state the snapshot age.
- Selling exactly at the limit is allowed. The pledge is the pledge.
- pump.fun changes to fee sharing or Holder Rewards could change how respawns work. Chain adapters are isolated so they can be updated.
- No promised value. Memecoins are collectibles. Nothing here is financial advice, and RESPAWN does not promise any outcome.