Verified lead
The CTO Registry lead
The takeover lead the Registry records for the token: the successor of a succession plan that triggered, or the lead its Roll Call elected. While that record exists, nobody else is the lead.
How does a community takeover get a website? If your token is on the CTO Registry and you are its verified lead, you make a free one page site here in about a minute: the contract, the chart, your links, the Roll Call count and the SCOUT report, built SI Ready. There is no code to write, no hosting bill and no domain to buy, and every site says plainly that it is a community page, not advice.
Free / Made by verified leads
A site appears here when its lead publishes it. Until then it is a draft only its lead can see.
Every count is real and started at zero on November 19, 2026.
Step 1
Sign in with your SI Passport and paste the token contract. The page checks that you are the verified lead of that token on the CTO Registry.
Step 2
A headline, up to three short blocks, your X and Telegram, one of six colors, and a logo and a banner if you have them. The name and ticker are read from the chain.
Step 3
One free signature and the site is live at codeflex.si/t/ followed by your ticker. Edit it, unpublish it or delete it whenever you like.
Loading the sites.
For verified leads
One site per token. Nothing is public until you publish, and a preview link shows you the draft exactly as visitors will see it.
Verified lead
The takeover lead the Registry records for the token: the successor of a succession plan that triggered, or the lead its Roll Call elected. While that record exists, nobody else is the lead.
Verified lead
The holder the token's Roll Call vote elected, one Passport and one sealed ballot each.
Verified lead
An admin of the Telegram group that verified the token's Registry page with /claim. You tie that Telegram account to your SI Passport with one tap in a private chat with the SCOUT bot, and SCOUT checks it again at least every 6 hours.
Verified lead
The official SI Passport of the token, for the six tokens of the SI ecosystem.
A token that is not on the CTO Registry cannot have a site here. A takeover joins the Registry when DEX Screener approves it, and its team then verifies the page with the SCOUT bot.
Live on every site
These parts are not written by the team. They are read from public records each time the page loads, so a site can never say more than the record does.
From the chain
The contract address on a single line with a copy button, and the chart and swap links made from that contract. Nobody types those links.
From SCOUT
How many SCOUT checks are clear, the holder count and a link to the full report: mint and freeze authority, top holders, the dev wallet and liquidity.
From the Registry
Whether the takeover is verified on the CTO Registry, the day DEX Screener approved it, and the takeover lead when the Registry records one.
From the holders
If the token has a Roll Call, the number of holders who answered still here, with a link to it. If it has Open Books or Clone Radar, the site links those too.
Every site carries "Built by Codeflex agents" with a path to the Studio, a plain disclaimer and a link to report it.
Why it matters
When holders take over a token, whatever site it had stays with the creator who left. The new team starts its first days with a contract and a group chat, and nothing a newcomer can check.
The supply of abandoned tokens
From August 1 to 28, 2026, MadeOnSol counted 1,032,440 token deploys on pump.fun from 223,339 wallets. 18,202 of them, 1.8%, graduated.
Source: MadeOnSol, pump.fun deployer stats for August 2026, published August 28, 2026, read November 19, 2026.
What it is and is not
It is
One page written by the verified lead of a takeover and hosted for free on codeflex.si. It gives a new team a place to send people on day one, with the record next to the words.
It is not
Codeflex does not check what a team writes beyond the guard, does not vouch for any token and says nothing about a price. A site promises nothing, and the community is not affiliated with Codeflex beyond the hosting.
Always
Never
If the Registry records a new verified lead for a token, for example after a dispute the Roll Call vote settled, the site passes to that lead as it stands, and the change is sealed.
Something wrong?
Every site links here. A report goes to the Codeflex team, who can unpublish a site. Its lead sees why.
Questions
The verified lead of a token on the CTO Registry signs in with the SI Passport on codeflex.si/takeover-sites/, writes a headline and up to three short blocks, adds the team's X and Telegram and publishes with one free signature. The site is live at codeflex.si/t/ followed by the ticker.
Only the verified lead of the token: the takeover lead the CTO Registry records, the winner of its Roll Call vote, its official SI Passport, or an admin of the Telegram group that verified its Registry page, tied to an SI Passport through the SCOUT bot. One site per token.
Nothing. There is no fee, no token to hold and no payment of any kind. Making and changing a site is a free message signature, never a transaction.
A headline of up to 80 characters, up to three blocks with a title and 400 characters each, one X profile link, one public Telegram link, a logo, a banner and one of six colors. No custom HTML, no scripts and no embeds.
Links and handles inside the text, any contract or wallet address but the token's own, price promises, anything that reads like a request for funds, keys or a wallet connection, and slurs. Links go only in the two link fields, where each is checked.
A site lives at codeflex.si/t/ followed by its ticker. You can point any domain you own at that address with a redirect at your registrar.
When the CTO Registry records a new verified lead, for example after the Roll Call vote settles a dispute, the site passes to that lead as it stands. The old lead can no longer change it, and the hand over is sealed.
Use the report link at the bottom of the site, or the form on this page. The Codeflex team reviews reports and can unpublish a site. A lead can always unpublish or delete their own.
Follow the work as it ships. The team posts what was built, what it cost and what comes next.