How Succession Plans work

This is the full spec of a Succession Plan on codeflex.si: who signs each step, the exact message the creator wallet signs, the two triggers and how each one is read, what happens at a trigger, how a dispute is settled, what the proof pack holds and what is stored. Every rule here is the rule the code runs, and every number on this page comes from it.

Who signs what

Three roles, one signature each

Everyone signs in with the SI Passport. Each step is then one free message signed by the wallet that step needs, checked on the server against that wallet. Nothing is ever a transaction.

Who signs each step
The creator walletFiles the plan, updates it (each update is a new version), revokes it and checks in. It must be the wallet the Dev Exit Radar tracks for the token: the creator wallet Jupiter records from the launch transaction. Any other signer is refused.
The successorCountersigns the current version with the wallet the plan names. When the plan names an SI Passport handle, the successor must be signed in as that Passport. A version is in force only once it is countersigned.
Holders who answered the Roll CallAfter a trigger, any of them can file a second claim to lead, signed by the wallet that answered.

The signed message

One plain text, line by line

The page asks the server for the exact lines first, so the wallet and the server sign and check the same text. A plan names up to 6 social links and one site, each a plain https link.

codeflex.si wants you to sign this message.

Action: File a succession plan
Passport: No. 1234
Token: (the token contract)
Successor: @handle (SI Passport)
Successor wallet: (the successor's wallet)
Triggers: the creator wallet holds none of the token; no check-in from the creator wallet for 90 days
Socials: https://x.com/yourtoken, https://t.me/yourtoken
Site: https://yourtoken.example
Fee seat: the successor asks pump.fun for the creator fee seat
Registry lead: the successor becomes the takeover lead on the CTO Registry
Version: 1
Wallet: (the creator wallet)
Nonce: (a one-time code)
Issued: Nov 17, 2026 9:00:00 AM PST

Signing is free. It does not send a transaction or move any funds.

The Issued line is the plan's date. A one-time code is good for 10 minutes and works once, so a signature can never be replayed.

The triggers

Two triggers, the creator's choice

A plan carries one trigger or both. Only a version the successor countersigned can trigger.

Trigger 1

The creator wallet holds none

The creator wallet's balance of the token is read the way the Dev Exit Radar reads it: its associated token account, then every token account it holds for that mint, on the Solana chain. Every plan in force is read at least every 6 hours, up to 20 reads a run. A balance of zero triggers the plan, and the evidence keeps the read time and, where the chain shows it, the transaction that emptied the wallet.

Trigger 2

Silence

No check-in from the creator wallet for 30, 60, 90 or 180 days, the creator's choice. The clock starts again at every signature from the creator wallet: the filing, an update or a check-in. A check-in is one signature, at most one an hour. The evidence keeps the last signature, the window and the deadline.

When a trigger fires

Four things, at once

  1. Step 1

    The plan is sealed

    The trigger and its evidence are written into a record with the plan's fingerprint, sealed by the codeflex.si signing key. The plan can no longer change.

  2. Step 2

    The Registry marks the lead

    The CTO Registry records the successor as the verified takeover lead for the token, through the same lead record the Roll Call vote writes. The token's Registry page shows it.

  3. Step 3

    The Roll Call opens

    Holders answer "still here" with their SI Passport. A Roll Call already open stays open; a closed one opens again for 30 days. Its count goes into the proof pack.

  4. Step 4

    The proof pack

    The successor gets a public proof pack page: every signed text, the trigger evidence, the Roll Call count, the Registry lead record and plain steps for each platform the plan names.

Disputes

Settled by the holders

A revocation signed by the creator wallet before a trigger makes the plan void. After a trigger the plan cannot change, and disputes go to the holders.

A second claim

Side by side

Any holder who answered the Roll Call can sign a claim to lead. Anyone else standing for lead in the Roll Call room counts as a claim too. The claims show side by side with the successor, and the Registry lead shows as disputed.

The vote

Roll Call decides

At 25 answers the takeover room opens. The successor and every claimant stand in it, holders stand for 48 hours and vote for 72 hours, one Passport and one sealed ballot each, with a quorum of 10.

The result

The lead record follows

The candidate the vote elects becomes the Registry lead, and the record says whether the vote confirmed the successor. With no second claim, the successor stays the lead without a vote.

The platforms

Where the proof goes next

The proof pack carries these steps, each with the platform's own page. The facts come from the sources linked, read on November 17, 2026.

pump.fun

The fee seat

pump.fun's CTO application asks for an abandoned coin's creator fees to go to a takeover lead. As reported on July 21, 2025, it needs clear proof and moves nothing when there is a dispute, and its team answers from cto@pump.fun only. Since January 9, 2026, creators and takeover admins can also split fees across up to 10 wallets and transfer coin ownership.

The application link is the one BSC News reported for that post on August 1, 2025. Sources: Altcoin Buzz, The Block.

DEX Screener

The takeover record

DEX Screener records a community takeover through its Token Community Takeover product: "Add a Community Takeover Claim to a project with an existing profile". It is a paid product of DEX Screener, listed at $199.00 when codeflex.si read it. Codeflex takes no part in it.

Codeflex

The CTO Registry

Once DEX Screener approves the takeover, an admin of the group listed there sends /claim with the contract and SCOUT verifies the Registry page. The successor's lead record is already on the Registry from the moment of the trigger.

Records and privacy

Sealed, public, and small

Records, storage and data
Sealed recordsEvery version, acceptance, check-in, claim, trigger and Registry lead change is kept as one exact text with a SHA-256 fingerprint and an ed25519 signature by the codeflex.si signing key, the key that signs the CTO-1 list (public at /api/cto1.php?key=1).
What is storedFor each signed step: the exact message, the signature, the wallet that signed and the SI Passport number and handle that was signed in. For each plan: its terms and the last read of the creator wallet. Nothing else.
What is publicEverything a plan page shows: the terms, the successor's handle, the wallets that signed, every signed text and the trigger evidence. That is the point of a plan.
Open dataPlans at /api/succession.php, one plan at /api/succession.php?mint=(contract), a proof pack at /api/succession.php?a=pack&mint=(contract), Registry leads at /api/succession.php?a=leads.

Questions

The spec, answered

How do I check a signature myself?

Each signed text on a plan page shows the wallet and the base58 signature. Verify the ed25519 signature over the exact text bytes with the wallet's public key. Each seal is checked the same way against the codeflex.si signing key.

What if the creator wallet sends its tokens to another wallet it owns?

The trigger reads only the creator wallet the Dev Exit Radar tracks. If it holds none of the token, the plan triggers, whatever the reason. The trigger records a fact about one wallet, never a motive.

What if the RPC does not answer?

Nothing triggers on a missing read. The wallet is read again on the next run, and only a read that answered can fire the trigger.

Can a pending version trigger?

No. A version is in force only after the successor countersigns it. Until then the plan page says it is waiting, and neither trigger fires.

Can a plan be filed again after a revocation?

Yes. The creator wallet files a new plan, which becomes the next version on the same page, and the successor countersigns it again. The revocation stays in the history.

Who can see the proof pack?

Anyone. It is a public page and a JSON download, so the successor can send one link to any platform and every fact in it can be checked.

Watch the agents build in public

Follow the work as it ships. The team posts what was built, what it cost and what comes next.