DexScreener CTO: what a community takeover is, and how to judge one

What a CTO is

A community takeover token is a token that is still trading but is no longer run by its creator. The contract keeps working, the liquidity pool (if it was not pulled) keeps quoting a price, and the chart keeps printing candles. What dies when a developer leaves is everything around the contract: the website, the X account, the Telegram, the marketing wallet. A CTO is holders rebuilding that layer and asking DexScreener to point the token's profile at the new community instead of the old one.

On DexScreener, "CTO" is therefore a specific status, not a vibe. Anyone can write "CTO" in a Telegram name; only DexScreener can attach the CTO label to a token page. When the takeover is approved, the profile links, description and images are replaced — the "cto update" people search for — and the token shows up in DexScreener's list of latest community takeovers, which is the list we track. A takeover is not the same as:

• a rebrand by the same developer (same people, new name — nothing was taken over),
• a relaunch on a new contract (a different token; the old holders are usually not carried across),
• a self-declared CTO on social media with no DexScreener approval (the profile still belongs to whoever paid for it first).

Why community takeovers happen

CTOs happen because the original team is gone and the token is not. In practice that covers a few very different situations, and which one applies matters more than the CTO label itself:

• The developer rugged. They sold their allocation, drained part of the liquidity or both, then deleted the socials. Whatever is left is what the community inherits — sometimes a working pool, sometimes almost nothing.
• The developer abandoned it. No theft, just silence: the launch did not go as hoped and they moved on to the next one. The chart bled out slowly rather than in one candle.
• The developer was removed. Doxxed, banned, or pushed out by the community after a dispute.
• There never was a team. On launchpad-style chains — Solana above all — thousands of tokens are created per day by people who never intended to run them. If one of those catches on, the "CTO" is in fact the token's first real team. Note that DexScreener only attaches the CTO label to a token that already has a paid profile; if nobody ever bought one, the community simply buys Enhanced Token Info and no takeover is recorded.
• A voluntary handover. Rare but real: the developer publicly passes the project, and occasionally contract ownership, to active holders.

The first two are the common cases. The difference between them — was money taken, and how much liquidity survived — is the first thing to establish when a CTO appears in the feed.

How a community applies for a CTO on DexScreener

A community applies for a DexScreener CTO by ordering the Token Community Takeover product on DexScreener's own marketplace, not through a third party. The product is described there as adding "a Community Takeover claim to a project with an existing profile", and as listed on the marketplace on 23 August 2026 it cost $199 (shown as reduced from $499), payable in crypto or by card (we re-checked the product page that day). The phrase existing profile matters: the takeover claim sits on top of an Enhanced Token Info profile that someone — usually the departed developer — already paid for. If the token never had a profile, the community is not taking anything over; it buys Enhanced Token Info like any other team (from $299 on the same date) and the page carries no CTO label.

DexScreener's public documentation says very little about the claim itself beyond the API, so the review criteria below are what the process looks like from the outside, not official rules. The current wording is always at docs.dexscreener.com and on the product page. In outline:

1. Get the community in order first. A live Telegram or Discord with named admins, an X account, ideally a simple site — and a clear, public record that the original developer is gone (last messages, wallet activity, deleted accounts). A handful of people with a fresh group is the kind of claim that gets refused.
2. Order the Community Takeover claim on the marketplace for the token's contract address, and submit the new logo, banner, description and links you want on the profile.
3. Provide the evidence. Who the admins are, where the community lives, and why the original team should be treated as inactive.
4. Wait for review. DexScreener checks the claim before the profile changes hands; approval is not automatic, and an original team that is still active can contest it.
5. Profile goes live under the CTO label. From that moment the new links are what visitors see, and the token appears in DexScreener's latest-CTO list — and, within seconds, in our CTO feed.

Marketplace prices change, so confirm the figure on the product page before paying. How the CTO claim compares with Dex Paid, boosts and ads is in the paid services guide.

DexScreener paid services: prices and what they do →

What changes on the profile — and what does not

A CTO changes the profile, not the token. After approval the token page shows a CTO label, the socials and website point at the new community, the description and images are replaced, and the existing Enhanced Token Info check-mark stays — the claim is attached to that profile rather than replacing it. That is the entire effect on DexScreener.

Nothing on-chain changes. The contract address, total supply, the developer's remaining holdings, the liquidity pool and its lock or burn status, mint and freeze authorities on Solana, contract ownership on EVM chains — all of it stays exactly as the original developer left it. A community takeover gives the new admins the token's storefront; it gives them no more control over the contract than any other holder has, unless the developer explicitly transferred ownership, which is uncommon and must be checked on-chain rather than taken from a Telegram pin.

This is why a CTO can be both real and worthless: the community is genuine, the profile is clean, and the developer still holds 30% of supply in a wallet that can sell into every rally the community builds.

How to evaluate a community takeover token

Evaluate a CTO like a new launch whose founders you can actually investigate, because that is what it is. The questions, in the order that eliminates bad ones fastest:

1. Liquidity. How much is left in the pool, is it locked or burned, and for how long? A rug that emptied the pool leaves a community taking over a token that cannot be traded at size. Check this before reading a single word of the new description.
2. The developer's bag. Where did the original allocation go? If it was sold, the overhang is gone. If it is still sitting in the deployer wallet, it is a standing sell order above every green candle.
3. Authorities and ownership. On Solana: is mint authority revoked, is freeze authority revoked? On EVM: is ownership renounced, and does the contract have hidden tax or blacklist functions? A takeover cannot fix a contract that the old developer can still manipulate.
4. The new team. Who are the admins — were they holders before the collapse, or did they arrive with the takeover? Do they have a history with other tokens, and how did those end? A team that has "CTO'd" several tokens in a row is a pattern worth pricing in.
5. Treasury. Is there a community wallet, how was it funded (donations, a new tax, the old marketing wallet), and who controls the keys? One admin with the seed phrase is a single point of failure; a multisig is a real governance step.
6. History. How high did the token get, how far did it fall, how many holders stayed, and what did the original team pay DexScreener for before leaving? Paste the contract into the token check: every Dex Paid profile, boost and ad campaign on that address, with the market cap at each payment, is listed in one place.
7. The CTO's own spending. A community that buys a 500x boost in its first hour is spending thousands of dollars — whose? Boosts and ads bought right after a takeover show up in the live feed and say a lot about who is really behind the "community".

If you only do one of these, do the first three. They are the ones that cannot be faked with a good Telegram.

Latest community takeovers on DexScreener

Below are the most recent CTO approvals DexScreener published, as our collector picked them up — with the market cap at the moment of the takeover and where each token stands now. The full list, filterable by chain, is in the CTO feed.

All community takeovers, live →

CTO compared with the other DexScreener badges

The CTO label is the only DexScreener status that says something about who is behind a token rather than how much they spent. The other three badges are pure budget signals.

How to read all of them together on a token page is covered in How to read paid activity on DexScreener.

CTOs in the DexScreener API

DexScreener's public API exposes the latest community takeovers as a list, alongside the latest token profiles, boosts and ads. The endpoint is GET /community-takeovers/latest/v1, rate-limited to 60 requests per minute, and each entry carries the token's chainId, tokenAddress, url, icon, header, description, links and a claimDate (per the official reference, checked 23 August 2026; a WebSocket stream of the same list is documented as well). Our collector polls that endpoint every few seconds, which is how a takeover appears on DXT Tools within moments of DexScreener approving it.

Like the other public endpoints it returns the current list only: no history, no market cap at the time of the claim, no outcome afterwards. We add those. Endpoints, rate limits and examples for the whole API are in the API guide.

DexScreener API guide →