$PHOENIX

Groups of wallets that keep buying the same coins: launch crews (they buy launch blocks together) and holder guilds (they sit among the top holders of the same coins). Only groups with 2+ wallets in this coin.

The 2 wallets that bought in the launch block (the first two blocks, under a second) took 19.9% of the supply. Grouped by the wallet that first funded them: 0 linked groups hold 0% of it.

Grey = a wallet with no funding link to the others. Taken out = sales minus buys plus liquidity out minus in, from the money-out measurement above.

The dev is one of 2 linked wallets; together they created 2 coins we checked; members bought 1 launch block.

Coins they created: $PHOENIX, $WIRED

Linked when one first funded the other, or both bought in the same small launch crew. Busy wallets (exchanges, services) are never used to join wallets.

The dev, the wallets that bought the launch block, and holders the dev funded: how they're connected and how their earlier coins did. The launch map below draws the connections.

1 of the wallets that bought this coin's launch block also bought the launch block of other coins we checked. Sniper bots and launch groups both look like this.

Creator wallet 86PXdSTFacRv7NBqDeLGN9bWUXqXcXZWG7T2H6ffSdkc (from GeckoTerminal). No other coins from this wallet in our records yet. Open the wallet ›

Who each of the biggest holders is to this launch, from the launch block, first funding, insider flags, known groups and each wallet's first trade.

Source RugCheck, read 28 Oct 2026.

The 20 biggest holders (bigger bubble = bigger share). Grey: pools and known services. Pink: wallets RugCheck flags as insiders. Same colour with a line to an outer dot: first funded by the same wallet. Liquidity locked: 100%.

Holders, insider flags, labels and liquidity locks: RugCheck. Shared funders: our own read of each wallet's first transaction.

The creator in the middle, the wallets that bought in the launch block around it (bigger bubble = bigger share of supply), and the wallets that funded them on the outside. Buyers with the same colour were funded by the same wallet.

What we find when we compare the coin's website, code, token, launch timing, liquidity, ticker and wallets against each other and against public address labels.

• Cabals in this coin1 known group of wallets is in this coin. The largest, holder guild #g93741, has 4 of its 38 wallets here: 0.21% held at our check. 15 of the 27 coins it was in with an outcome fell 80%+ within a day. source
• Linked walletsThe dev is one of 2 linked wallets; together they created 2 coins we checked; members bought 1 launch block. source
• The teamThe dev and 1 early buyer/holder wallet; their 5 earlier coins with an outcome: 5 fell 80%+, 0 went 2x+ within a day. source
• The story behind itThe coin's story is an X post by @grok12_john (verified) with 15 likes. The post names this coin. 4 other coins we checked use the same post. source
• Website doesn't show this token's addressThe token's address doesn't appear on its website or in the site's code. source
• Website age vs launchThe Internet Archive first saved the site 6740 days before the coin launched. source
• Code linkedThe site links to https://github.com/security/advanced-security; its check is queued.
• Reused X postThe X post x.com/grok12_john/status/2115277023341854918 is also listed by 4 other coins we checked: $Phoenix, $Phoenix, $Phoenix, $Phoenix. So many coins list it that it's most likely someone else's, borrowed for the story. source

How earlier coins with the same signals did: the share that fell 80% or more within 24 hours of our check, against coins without the signal. It describes past coins; it doesn't predict this one. All signals

• Checked isn't the same as safe: these checks describe what the token allows and what the website runs, not what anyone will do.
• "Nothing found" means not visible on the public page; servers and private code are invisible to us. Not financial advice.