CTO-1

The open standard for community takeovers. Eleven rules a real takeover can meet: seven checked automatically from the chain and four reviewed by Codeflex. Free, public and versioned.

Version 1.0 / Eleven rules

The standard

Seven rules are read automatically from the chain and the CTO Registry. Four are reviewed from the proof the team sends. A takeover that meets all eleven is CTO-1 verified.

  1. CTO-1.1

    Clean contract

    Mint authority and freeze authority are both revoked, so nobody can print more tokens or freeze a holder.

    Automatic
  2. CTO-1.2

    No hidden creator bag

    The wallet that created the token holds under 1% of the supply.

    Automatic
  3. CTO-1.3

    Supply not concentrated

    The ten largest wallets hold under 50% of the supply.

    Automatic
  4. CTO-1.4

    Approved takeover record

    The takeover has an approved record on DEX Screener and is on the Codeflex CTO Registry.

    Automatic
  5. CTO-1.5

    Team proven

    An admin of the token's listed Telegram verified the Registry page through the SCOUT bot.

    Automatic
  6. CTO-1.6

    Contract on the official site

    The official website shows the exact contract address.

    Automatic
  7. CTO-1.7

    Active market

    At least $10,000 of liquidity or $5,000 of daily volume.

    Automatic
  8. CTO-1.8

    Team tokens locked or burned

    Any supply the team holds sits in a public lock or has been burned, with the links published.

    Reviewed
  9. CTO-1.9

    Treasury on a multisig

    The community treasury sits in a multisig wallet, and its address is published.

    Reviewed
  10. CTO-1.10

    Public roadmap

    A public roadmap page says what the team plans next.

    Reviewed
  11. CTO-1.11

    Proof page

    A public page lists the official wallets, locks and burns.

    Reviewed

New versions are published here with notice before they apply. Verified tokens are re-checked every week.

Any takeover

Check a token against CTO-1

Paste a Solana contract to see every check, read live.

Signed list

CTO-1 verified

Every verified takeover, in the token list format wallets and exchanges already read. The list is signed, so anyone can check it came from Codeflex.

Loading the verified list.

The list

https://codeflex.si/api/cto1.php

The signing key

https://codeflex.si/api/cto1.php?key=1
  1. Step 1

    Fetch the list

    The answer holds the list, the exact signed text and an ed25519 signature.

  2. Step 2

    Check the signature

    Verify the signature over the signed text with the public key from the key link.

  3. Step 3

    Show the tag

    Mark every listed contract as CTO-1 verified, and link to its Registry page.

For takeover teams

Apply for CTO-1

Your token must be on the CTO Registry, and CTO-1.5 needs your team verified with the SCOUT bot first. Send the four proofs and the team reviews them by hand.

Free. Your details go only to the Codeflex team. Contact details are never shown on the site.

Founding seats open

Co-sign the standard

Codeflex invites wallets, DEXs, screeners, security firms, exchanges and launchpads to review CTO-1, shape the next version and show the tag to their users.

Your details go only to the Codeflex team. Contact details are never shown on the site. Approved reviewers are listed on this page by name.

Questions

CTO-1, answered

What is CTO-1?

An open, versioned standard for what a real community takeover publishes and proves. Version 1.0 has eleven rules: seven checked automatically from the chain and the Registry, and four reviewed by Codeflex from the proof the team sends.

Does CTO-1 mean a token is safe to buy?

No. CTO-1 says a takeover is run in the open: clean contract, no hidden bags, a proven team, locked team tokens and public proof. It is never a price call, and nothing about it is advice.

How does a team get verified?

Get on the CTO Registry, verify the team with the SCOUT bot, then send the four proofs with the form on this page. When the automatic checks pass and the proofs check out, the token is verified and gets the CTO-1 badge.

Can verification be lost?

Yes. Every verified token is re-checked each week. If an automatic check fails, the status changes to lapsed until it passes again. Codeflex can also remove a status if a proof stops being true.

How can a wallet or exchange use it?

Read the signed list at codeflex.si/api/cto1.php in the familiar token list format, check the signature against the public key at codeflex.si/api/cto1.php?key=1, and show the CTO-1 tag. Organizations can also apply to co-sign the standard as reviewers.

What does it cost?

Nothing. Applying, verification, the badge and the list are free.

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.