Skip to main content

​
Community takeover (CTO)

If we find bot activity (coordinated accounts, fake personas, anything we can flag as inauthentic), the ticket is closed with no further notice and every wallet and handle attached to the claim is banned from all official token channels. There is no appeal.
A CTO is what happens when the original creator walks away and the community picks up the project. Two things move: the token’s socials on its Snekfun page (X, Telegram, website, Discord, description, image) and the creator-fee wallet that collects trading fees.

​
When a token is eligible

A token qualifies for CTO review when all of the following are true:
CriterionRequirement
Splash graduationThe token has graduated to Splash DEX
Social silenceNo posts on the token’s official X, Telegram, or Discord for ≥ 7 days, or the token has no socials at all
Holder baseAt least 50 unique holders
Claimant stakeThe new dev address holds ≥ 1% of circulating supply at a Snekfun-defined snapshot block
Borderline cases get reviewed too. If you think there’s a real abandonment story but you fall short on one row, open a ticket anyway.

​
The process

1

Open a Discord ticket

Open a ticket in our Discord and post your claim using this message:
Snekfun CTO claim

Token: https://snek.fun/token/<policyId>

New dev address:
addr1...

Proposed new socials:
- X: @handle
- Telegram: t.me/...
- Website: https://...
- Discord: discord.gg/...
Wallet ownership proof. Once the ticket is opened, Snekfun replies with a fresh 16-byte verification code. Send 1 token of the project from your new dev address back to that same address (a self-transfer) with the code attached as transaction metadata. Drop the transaction hash into the ticket. A missing, mismatched, or stale code fails verification.Social ownership proof. Post the same 16-byte code on each of the proposed new socials (X, Telegram, Discord, website if applicable), together with a short statement that you intend to take over as CTO leader of the token. Drop the links into the ticket. The Snekfun team reviews the accounts to confirm they are run by the same person opening the ticket.
2

Triage and execution

The Snekfun team checks the eligibility criteria above, verifies the self-transfer and the public posts on the new socials, and confirms no other CTO ticket is already open for this token.If everything checks out, we make the change: the creator-fee wallet is repointed to your new dev address, and the socials, description, and image on the token’s Snekfun page are replaced with your submitted values.If the claim is rejected on technical grounds, you get a written reason.

​
After a CTO

  • A second CTO against the same token cannot be filed for 90 days after execution.
  • The new lead has the same rights as any token creator: update socials, withdraw creator fees. As with every token on Snekfun, those changes still pass through team review before they go live.
  • The history sticks around. Snekfun keeps a permanent public record of every CTO on the token’s page.