Go ProSign in

← blog · 2026-10-21 · 7 min read

Kimchi Token Launch: What the On-Chain Data Shows

The Kimchi token launched on Pump.fun on 20 Oct 2026 amid insider allegations. What's on-chain, what's alleged, and how to spot the same launch patterns.

On the evening of 20 October 2026, a token called KIMCHI launched on Pump.fun and was worth close to $40 million on paper within an hour. It launched at almost the same moment Pump.fun announced a creative partnership with the pseudonymous trader it was named after. Within hours, X was asking the usual question: who knew?

This post separates what the on-chain record shows from what has been alleged. It then turns the case into a checklist you can use on any launch, including the ones on the hoodwatch.dev tape.

Quick note: hoodwatch.dev is unofficial and read-only. It isn't affiliated with fomo.family, Pump.fun or Robinhood. Nothing here is financial advice, and nothing here accuses any named person of wrongdoing. Where a claim hasn't been verified, we say so.

What happened: the timeline

All times below are UTC unless marked otherwise.

What the on-chain record shows

Most of the detailed numbers come from Bitquery's investigation, published 21 October. Bitquery says it checked each figure against raw Solana data.

The deployer took most of the supply in the launch transaction. The launch transaction bought 793 million of the 1 billion tokens for 85 SOL (about $9,073), which filled the bonding curve in one go. The first outside buyer paid 3.8 times the deployer's price. So in practice the token never had an open bonding-curve phase that the public could buy into.

75% of supply went to one wallet. Fifty-seven seconds after launch, the deployer sent 750 million tokens to a single wallet. When Bitquery published, that wallet had not sold any of them. Bitquery says the wallet "has been widely flagged on X" as belonging to the namesake trader, and states plainly that it did not verify this.

The deployer had rehearsed. That afternoon, the same deployer launched four test tokens, each with roughly a $1 buy that was sold within about 30 seconds. Less than four hours after KIMCHI, it launched a second KIMCHI and another token, each opened with an 85 SOL curve-filling buy and sold off within 18 seconds. Bitquery counts 33 Pump.fun tokens from this deployer since 23 July. The deployer's own profit on KIMCHI was about $26,000.

A linked cluster switched tokens within a minute. Three wallets held 5.19 million of the old KIMCHI. Forty seconds after the new token was created, they began buying it, with one buy from each wallet at the same instant. Nineteen seconds later, all three sold their entire old-KIMCHI position in a single block. By 23:09 they had turned $7,332 of new KIMCHI into $111,748. Bitquery links the three through 129 direct transfers to one another since January, and found two of them entering this deployer's July and August launches two seconds after creation.

Bitquery found no direct transfer between that cluster and the new deployer, the old token's creator, or the 75% wallet. In its words, the ledger "cannot show what anyone knew".

What is alleged

Response so far: the public statements we found are the co-founder's endorsement of the partnership. We found no statement from Pump.fun or the trader that addresses the insider allegations directly. If one appears, we'll update this post.

A note on Pump.fun's fees

KIMCHI launched three days after Pump.fun changed its fees. Pump.fun's fees page (last updated 17 October 2026) says that from 17 October, trades through its web and mobile apps carry a 0.45% platform fee (0.40% with a referral code). Crypto Briefing reports that Solana trades through the mobile app are fee-free, alongside that platform fee, and Pump.fun says the platform-fee revenue goes to referral and callout rewards. Either way, cheaper and more social trading means more people arriving early and fast at launches like this one.

How to spot these launch patterns yourself

KIMCHI is a Solana Pump.fun story, but each of its patterns turns up on fomo.family tokens on both Solana and Robinhood Chain. Here's what to check.

1. Supply taken in the launch transaction

If the deployer's first buy fills most of the curve, the public's "early" entry is actually a much higher price. Look at the first buy in the creation transaction and at what share of supply it took. On Robinhood Chain launchpads, the equivalent is the anti-snipe exemption list. See Pons launchpad explained.

2. One wallet holding a huge share

A single holder with 75% of supply can end any chart with one sell. Whether it is "locked by reputation" is a belief, not something you can check on-chain.

3. Synced or bundled buys

Buys of the same size from several wallets, landing at the same instant or in the same block, are the fingerprint of one operator. Real crowds are messy. The hoodwatch tape shows a synced-buy flag when fresh wallets cluster like this.

Wallets that fund each other or sweep into one collector are not independent buyers. Trace where the first buyers' gas or SOL came from. If the trail leads back to one source, treat them as one wallet.

5. Deployer history

Test launches, serial relaunches and quick curve-filling dumps are visible in a deployer's past tokens. hoodwatch's deployer flag marks tokens whose creator has a history worth checking.

6. Copycats and vamps

KIMCHI reused the name and ticker of an existing token. If two contracts share a ticker, check which one you're actually buying. The copycat flag catches the common cases.

Using hoodwatch

Paste any contract into the scanner at /scan before you buy. It checks for honeypot behaviour (you can buy but not sell), VANISH (balances disappearing without a sell), empty-pool bait, copycats and deployer history. You can also browse what others have checked recently at /scans. For the full checklist, read how to spot a rug pull on fomo.family.

A clean scan doesn't mean a token is safe. KIMCHI had no honeypot problem: the risk came from the supply structure and who got in first. Read the flags together with holder concentration.

FAQ

What chain is the Kimchi token on?

Solana. It launched through Pump.fun at contract CSocnzcRpgSCr1naKcNTieWZUxb6rABe45j844m7pump. An older, unrelated KIMCHI token with the same name exists, so check the address.

Was the Kimchi launch insider trading?

That hasn't been established. On-chain data shows a concentrated supply and a linked wallet cluster that profited in the first minutes. Claims that anyone had advance knowledge remain allegations.

What is a vamp?

A new token launched under an existing token's name and ticker, timed so that buyers move to the copy. The old KIMCHI lost most of its value within 15 minutes.

Can hoodwatch tell me whether to buy?

No. hoodwatch is a read-only tape and scanner that shows on-chain risk signals. It doesn't give financial advice, and new memecoins carry a high risk of total loss.


hoodwatch.dev is unofficial and read-only, not affiliated with fomo.family or Robinhood. Nothing here is financial advice. Open the live tape.

Is fomo.family safe? An honest fomo.family review

Is fomo.family safe? A neutral review of the app's custody model, fees, chains and track record, and the token-level risks no app can remove for you.

How to Spot a Rug Pull on fomo.family Before You Buy

A practical checklist for spotting a rug pull on fomo.family: honeypots, vanishing balances, synced buys, empty pools, copycats and deployer history.

Pons launchpad explained: snipe tax and exempt wallets

How the Pons launchpad on Robinhood Chain works: the 99% anti-sniping tax, how it decays, the 32-wallet exemption list and how to spot it being abused.