A crypto project Twitter handle change leaves a record you can read before you ever reply to the team. NAUT stores the X handle trail GMGN keeps against a company row for 178 live rows, read on 9 November 2026, and 89 of those hold 2 or more handles; 16 rows carry GMGN's community-takeover flag, and 10 of the 16 sit inside that group of 89. This article runs 3 checks on those 10 rows and works them through on 1 of them, Caesar.
Data note. Every count here was read from NAUT's own database on 9 November 2026, read-only. The X handle rename history and the flags are GMGN records stored against a NAUT company row: gmgnHandleHistory, where each entry is a handle with the date it was taken, and gmgnTwitterFlags, which holds cto_flag, twitter_create_token_count and twitter_del_post_token_count. 178 live, unmerged company rows hold at least 1 handle entry, 89 hold 2 or more, and 16 carry cto_flag set to 1, of which 6 carry the flag with an empty handle trail. 6 claims in this article were put to outside sources: 2 came back confirmed, 2 contradicted, and 2 could not be read at all, because the Solscan page and the GMGN page for the Caesar mint each returned HTTP 403 to NAUT's fetch. The handle trails of the 10 rows tabled below were not re-read outside NAUT, apart from Caesar's, and that check did not confirm it, which is why the worked example ends in a step you run yourself. 1 further row in this pull was left out as a data defect: its 4 stored handles do not read as 1 company's own trail, so the GMGN record looks bound to the wrong company. NAUT Research wrote it.
Nothing here says any project did anything wrong. A flag and a handle trail are inputs to a question you put to the team, and 1 of the rows below is a public rebrand that the row's own description already names.
How do I check a crypto project Twitter handle change in 3 steps?
These 3 crypto rug pull checks run off stored fields, so they cost nothing and take about a minute: open the project's NAUT page, read the 3 fields in order, then ask the team about whatever the fields leave open.
- Check 1, the handle trail. Count the handles on record and read their dates. 89 of the 178 rows with a trail hold 2 or more, so a second handle is common; the shape that earns a question is a trail of 3 or 4 inside 1 year. Roam holds 4 entries, the longest trail in the table below, and the dates sit on the row's own NAUT page beside each handle.
- Check 2, the takeover flag.
cto_flagset to 1 marks a community takeover token. The crypto.news explainer of the term describes it as "when the holders or broader community of a token take over running the project after its original developers abandon it", read on 9 November 2026. 16 live NAUT rows carry that flag. - Check 3, the account's own token count. GMGN keeps 2 counts against the X account, stored as
twitter_create_token_countandtwitter_del_post_token_count. Across the 10 rows below the first runs from 5 to 507; on the worked example, Caesar, the second stands at 1. GMGN's own token page returned HTTP 403 to NAUT's fetch on 9 November 2026, so these are NAUT's stored values and were not re-read at the source.
- Read the handle trail89 of the 178 rows with a trail hold 2 or more handles, and Roam holds 4, the most in the table below.
- Read the takeover flag16 live rows carry GMGN's cto_flag set to 1, and 10 of those also hold 2 or more handles.
- Read the account's token countThe 10 run from 5 on Elixir Games to 507 on Moonbirds.
- Put the gap to the teamAsk which handle the project used at its raise, who holds the account now, and what the older handles were.
Which projects carry a handle change and a takeover flag on NAUT?
These are the 10 live NAUT rows that hold 2 or more handles on record and also carry GMGN's cto_flag set to 1, read on 9 November 2026. The list is ranked by the number of handles on record, then by the token count on the account.
| Project | Handles | Token count |
|---|---|---|
 Roam |
4 | 37 |
 Sonic (prev. Fantom) |
3 | 69 |
 XMAQUINA |
3 | 37 |
 HivelloOfficial |
3 | 31 |
| Mixie | 3 | 11 |
 Moonbirds |
2 | 507 |
 Sonic |
2 | 251 |
 Assisterr |
2 | 131 |
 Caesar |
2 | 91 |
 Elixir Games |
2 | 5 |
2 rows in that table carry the same name, and they are 2 separate NAUT rows: Sonic (prev. Fantom) is the Layer-1 chain whose own NAUT description names Fantom as its predecessor, and Sonic is the row whose description names an L2 network on Solana. That pair is the reason check 1 stops at a question: a trail of handles fits a public rebrand as well as it fits an account changing hands.
The handle strings and their dates sit on each row's own NAUT page, 1 entry per rename, and they are worth reading beside the handle the row stores today: the 2 fields can disagree, as they do on Caesar below, where the trail starts on a handle the account no longer uses.
How many other tokens sit against the same X account?
The bars are GMGN's twitter_create_token_count as NAUT stores it, highest first: 507 on Moonbirds, 251 on the Solana L2 row Sonic, and 5 on Elixir Games. The second count, twitter_del_post_token_count, is stored on the same record and read the same way; on Caesar, the row worked through below, it stands at 1 against a create count of 91, so read it per row on the project's own page. Both numbers are GMGN's record of the X account, so treat a high one as a line to raise with the team.
Worked example: Caesar, 2 handles on NAUT's record
- Stored X handle: @caesar_data. That handle came back confirmed on 9 November 2026, on the account itself and on a second page that lists the project beside
caesar.xyz. - Handle trail on NAUT: @telenomic, dated 2025-01-14, then @caesar_data, dated 2025-05-10.
- Takeover flag:
cto_flagset to 1. - Token counts on the account:
twitter_create_token_count91,twitter_del_post_token_count1. - Stored description: "Deep research assistant powered by AI".
The rename is where this stops being a desk exercise. NAUT's record holds the trail above, and the outside check of that rename did not confirm it: the search found no prior @telenomic account and no rename notice, and a public post from April 2025 already tags @caesar_data. The source check of the stored description did not confirm it either. The 2 pages that would settle the mint, Solscan's token page and GMGN's token page, each returned HTTP 403 to NAUT's fetch on 9 November 2026.
So the honest output of 3 checks on this row is 3 questions for the team rather than a verdict: which handle were you using in January 2025, who holds the account today, and what are the other tokens GMGN counts against it. The Caesar page is where you find the people to ask.
What does a crypto project Twitter handle change tell a deal maker?
- It dates the account against the deal. A trail of 4 entries, as on Roam, tells you the account is older than the name it carries now, and each entry on the row's page has its own date.
- It separates a rebrand from a swap. Sonic (prev. Fantom) carries 3 handles and a description that names the predecessor, so the trail and the story agree.
- It gives you 1 question that gets answered. "Which X account did you raise under" is cheap to ask and hard to dodge, and the answer either matches the trail or it does not.
- It thins a list rather than ranking one. 16 of the rows NAUT holds carry the flag, so this check pulls a handful of rows out of a target list for a closer read.
- The record can be wrong. 1 row in this pull was dropped because its 4 stored handles look like a GMGN record bound to the wrong company, so read the trail beside the row's own description and its own site.
- Open the row before the call10 live rows hold 2 or more handles and GMGN's takeover flag, from Roam at 4 handles down to Caesar at 2.
- Date the trailEach entry on the row's page carries its own date, as on Caesar: @telenomic on 2025-01-14, then @caesar_data on 2025-05-10.
- Cross-read the descriptionSonic (prev. Fantom) names its predecessor in its own NAUT line, so its 3 handles read as a rebrand.
- Send 1 question to a named personEach project page above lists the team NAUT holds for that row, with the channels on file.
Related reading on NAUT: How to verify a crypto investor: 6 checks, 143 funds pass 4 and Crypto contact data accuracy: 86 of 100 X handles, 0 suspended.
Can you pull this data through the NAUT API?
Every project named here has a record you can pull: GET https://api.naut.so/v1/projects/caesar returns that company with its team, and GET https://api.naut.so/v1/projects?q=sonic searches the directory when you have a name rather than a slug. A data call costs 5 credits, with the key sent as $NAUT_KEY in an Authorization: Bearer header; the endpoints are at naut.so/docs/api and the plans, from Essential at $49 a month for 3,000 credits, at naut.so/pricing. Verified Telegram, email and LinkedIn on a person's record unlock on any paid NAUT plan, so start a 7-day trial if you need to reach the team behind 1 of these rows.
Crypto project Twitter handle change FAQ
How do I know if a crypto project changed its X handle?
Open the project's page on NAUT and read the stored handle trail, which is GMGN's gmgnHandleHistory: each entry is a handle with the date it was taken. NAUT held at least 1 entry for 178 live company rows on 9 November 2026 and 2 or more for 89 of them, so the trail is the fastest place to see a change, and the project's own team is where you confirm it.
What does a community takeover flag mean on a crypto token?
It marks a token whose original developers walked away and whose community took over running it, which the crypto.news explainer read on 9 November 2026 describes as "when the holders or broader community of a token take over running the project after its original developers abandon it". 16 live NAUT company rows carried GMGN's cto_flag set to 1 on 9 November 2026, and 10 of those also held 2 or more handles on record.
Does a handle change mean a project is a rug pull?
No. 89 of the 178 rows with a stored trail hold 2 or more handles, which is too many to read as a warning on its own, and Sonic (prev. Fantom) carries 3 handles against a NAUT description that names Fantom as its predecessor. Treat a trail of 3 or 4 handles inside 1 year, a takeover flag and a high token count on the account as 3 reasons to ask the team a question before you sign anything.
How many other tokens does GMGN count against these accounts?
Across the 10 flagged rows the stored twitter_create_token_count runs from 5 on Elixir Games to 507 on Moonbirds, with 251 on the Solana L2 row Sonic and 91 on Caesar. GMGN's own token page returned HTTP 403 to NAUT's fetch on 9 November 2026, so those are NAUT's stored values as of that read.
Where can I find these 10 projects and the people behind them?
All 10 have a NAUT project page, linked in the table above, and each page lists the team NAUT holds for that company with the contact channels on file. You can pull the same records through the API with GET https://api.naut.so/v1/projects/caesar at 5 credits a call, and verified Telegram, email and LinkedIn unlock on any paid NAUT plan, so start a 7-day trial when you need the person rather than the page.
Sources
- NAUT's own database, read on 9 November 2026, read-only:
gmgnHandleHistoryandgmgnTwitterFlagson live, unmerged company rows, plus each row's stored name, X handle and description. Every count above was computed from those rows at that time. - The X account @caesar_data, read on 9 November 2026, and a second page listing the project beside
caesar.xyzoncoincarp.com. Together they confirmed the handle NAUT stores for Caesar. - The crypto.news explainer of a community takeover,
crypto.news/what-is-a-community-takeover-cto-when-a-memecoins-holders-seize-the-wheel/, read on 9 November 2026, for the quoted definition of the term behindcto_flag. - Searches of X and the open web for a prior @telenomic account and a rename notice, run on 9 November 2026: they did not confirm the rename NAUT's record holds, which is reported above as the check's own result.
solscan.ioandgmgn.aitoken pages for the mint stored against Caesar: each returned HTTP 403 to NAUT's fetch on 9 November 2026, so neither is used as a source for any number here.