Verified lead
The CTO Registry lead
The takeover lead the CTO Registry records for the token: the successor of a succession plan that triggered, or the lead its Roll Call elected.
Codeflex
Language
249 languagesTranslated on this page by Google Translate. Contracts, prices and live numbers stay exactly as they are.
What happens to my community if the Telegram group is gone? Without a backup, its members scatter with it. The Lifeboat is that backup, made before it is needed: members board by tapping the SCOUT bot, and if the group is deleted, hacked or left by its dev, the community's verified lead launches the Lifeboat and the bot messages every member who boarded the new group link. It is free, and the bot only ever messages people who started it.
Board in one tap
Find your community, tap Board and press Start in Telegram. That is all. Members show here as a count, never as names.
Every count is real and started at zero on November 17, 2026.
Step 1
Every registered Lifeboat is listed below with its member count and whether its lead is verified.
Step 2
Telegram opens the SCOUT bot. Press Start and you are aboard. SCOUT keeps your Telegram user id and the Lifeboat, nothing else.
Step 3
Optional: the bot gives you a one-time link that works for 30 minutes. Linking adds the Lifeboat crew stamp to your SI Passport when stamps are on.
Loading the Lifeboats.
How a launch works
Only a verified lead can launch, only with a t.me link, and never more than once in 7 days.
Step 1
The verified lead signs a launch with the new group's t.me link, the reason (deleted, hacked or abandoned) and a short note with no links in it.
Step 2
A public notice runs on the Lifeboat's page first, with the new link and who launched it. The lead can cancel, and members aboard can report it as wrong.
Step 3
SCOUT sends every member aboard one plain text message: the community, the new link, who launched it and when, and the proof link. Sends are queued at up to 25 a second.
Step 4
The launch and its delivery counts are sealed. A launch members report as wrong is flagged on its page for review by the Codeflex team.
For community leads
Sign in with your SI Passport, give the community's name, its token contract if it has one and its current group link, and sign once. Members can board right away. Launching needs a verified lead.
Verified lead
The takeover lead the CTO Registry records for the token: the successor of a succession plan that triggered, or the lead its Roll Call elected.
Verified lead
The holder the token's Roll Call vote elected, one Passport and one sealed ballot each.
Verified lead
The official SI Passport of the token, one of the six official accounts of the SI ecosystem.
Verified lead
An admin of the group that verified the token's CTO Registry page, checked by SCOUT once the admin boards and links the same SI Passport.
Any other lead is listed as "lead not verified": members can board, and the Lifeboat cannot launch until its lead is verified. One Lifeboat per token; a verified lead can take over the token's Lifeboat from an unverified one, and the members stay aboard.
The rule card
The Lifeboat keeps as little as it can and says exactly what it does.
Always
Never
Telegram's rules for bots, read November 17, 2026: bots cannot start conversations with users (core.telegram.org/bots), and for bulk notices a bot can send about 30 messages a second, and no more than one a second in a single chat (Bots FAQ).
What it does and does not do
It does
It keeps a list of people who chose to be reached, and it reaches each of them once with the new link, the name of the lead who launched it and the proof page.
It does not
Codeflex does not run the new group, cannot restore a deleted one and says nothing about a token or its price. A launch shows who launched it and why, in public, and members decide for themselves.
Questions
If the community has a Lifeboat, its verified lead launches it with the link of a new group. After a 30 minute public notice, the SCOUT bot sends every member who boarded one plain text message with the new link, who launched it, when, and the proof link on codeflex.si.
Tap Board next to your community on this page, or on its own Lifeboat page. Telegram opens the SCOUT bot; press Start. SCOUT keeps your Telegram user id and the Lifeboat id, nothing else.
Only its verified lead: the CTO Registry's takeover lead for the token, the winner of its Roll Call vote, its official SI Passport, or an admin of the group that verified its Registry page. A Lifeboat whose lead is not verified cannot launch.
No. Pages show the number of members only. SCOUT never forwards or stores messages from any group, never stores phone numbers and never publishes who boarded.
Send /leave to SCOUT to leave every Lifeboat, /leave followed by a Lifeboat id to leave one, or press Leave this Lifeboat in the bot. Leaving deletes your boarding record. /lifeboats lists the ones you boarded.
Send /wrong followed by the launch number in the message, or report it on the Lifeboat's page with a linked SI Passport. The launch is flagged on its page and the Codeflex team reviews it. The lead can also cancel during the public notice.
A launch accepts a public group link like t.me/yourgroup or an invite link like t.me/+code, and nothing else, so a launch can never send members to another site. A public group name goes through the same guard Roll Call uses.
No prize and no payment. Members who link their SI Passport get the Lifeboat crew stamp when stamps are on. The stamp says you are crew, never which community.
Follow the work as it ships. The team posts what was built, what it cost and what comes next.