THE CRIERS

KOL LIST

Nothing on chain names a KOL. A handle opens a tab only when a public source ties it to the deployer wallet or the token it launched. Every entry links that source.

1 entries · curated 2026-09-13

The Crier with the neon megaphone
HANDLEDEPLOYER WALLETSLAUNCHES FOUNDSOURCEWHAT TIES THEM
@byVLTNO0xbc49…70ac1source ↗Lucky Horse - $幸运马 The Year of the Horse Mascot. Chinese meta, genny lore.https://t.co/zogQwx5p1X DEX at 30k 0xfc8305007504b062aFE71bc8c4f34F3ac0f196d1 13k
PARTIAL: the tweet ties @byVLTNO to the token CA only. The tweet does not say he deployed it; the listed wallet is the on-chain TokenLaunched creator of that CA, not a wallet the handle claimed.

What curation found: No public source found where a KOL claims a deployer wallet. Sources tie handles to token CAs; in every checked case except @byVLTNO the source itself says someone else deployed.

Checked and not listed (10)
  • @frankdegods ($FRANK 0x06226177372c7240a1c815938002b6e3f66122e6)
    onboardthem.fun/explore lists the coin "for @frankdegods", but Onboard's docs say "A launcher picks a name, image, and a creator" and "Your wallet signs": the TokenLaunched creator 0x8392dde4bfcca159fc576286779a96acc313effc (block 56773326, tx 0x05f7667a67934450ab05f46b7c96971ccaa07a5176ce71d674e46dfcc814cad0) is the third-party launcher, not frank. That launcher has 2 pons v2 launches, including 0x5d7ddd076c13a70b63f0bd0c95bf0cb0ab87c573 listed on Onboard "for @theunipcs", so it launches for several KOLs. frank's fomo.family wallet 0x696d1265c8fc4f14797abebfae3c43ebfa9d8e28 is a different address.
  • @slash1sol ($GT 0x10ba3988aa0a9db5f2a262e1c2c7081aba1b5273)
    Tweet (oEmbed-verified) posts the CA but says "A TOKEN LAUNCHED AROUND IT ON ROBINHOOD ... fees route to me": he is the fee recipient, not the deployer. TokenLaunched creator 0xe7f1c04e796f48820e5e41fcc8743343a3043bfe (block 50824416) is not claimed by him; no CreatorFeeRecipientUpdated log for this token.
  • Him (@himgajria) / COPPERINU 0x5317c0d077d2eeb639448939b930d49c4984b63b
    ChainCatcher: "COPPERINU was deployed by the Pons Vault developers, who sent 40% of the tokens to crypto KOL Him's wallet." Him is a recipient/holder, not the deployer; TokenLaunched creator is 0x98469ccf8b1807870f61557aea293adf959bc212 (18 pons v2 launches), no public post ties it to a KOL.
  • @theunipcs (Unipcs) / UNIPCS 0x7df5daaf80e65dfcc7a1435d9b52bcf2b5753fbe (MADE) and UNIPCS 0x5d7ddd076c13a70b63f0bd0c95bf0cb0ab87c573 (Onboard)
    MADE (mademen.family) seat token that pays unipcs a fee share; his fomo wallet 0x0a6ebed0155edb4b21d92ad02897a626cd90119e is listed as trader, not deployer (TokenLaunched lookup for 0x7df5 was cut by RPC 429, not verified). The Onboard coin "for @theunipcs" was launched on pons v2 by the same third-party launcher 0x8392dde4bfcca159fc576286779a96acc313effc that launched $FRANK.
  • @MEADGod (Ozzy, pons founder) / 赢 0x1fc5106c7940189724b48de2dcd7161e48fc3452
    DEX Screener links the token to his tweet "让我们赢吧", which has no CA or wallet; he is the platform developer, not a KOL. Creator 0x9e021739174c058a8947182f2659f9639f6ae8d0 not tied to him.
  • @trenchenjoyor / LUOBINXIA 0xb7b0cad6e560bda279f238a42c695cb2b1681227
    DEX Screener links a lore tweet with no CA or wallet; no KOL evidence. Creator 0x920a7920911441b2d8694e6a69a57267a0387238 not tied to the handle.
  • @Tanaka_L2
    Trader/commentator posting about pons tokens; no post found tying the handle to a deployer wallet or to a token he launched.
  • Token project accounts (@hood4663_rh, @thinkingcatRH, @CorruptedQtrns, @OGJimothyPons, @rabbit_rhs, @ponsflow, @trychinapad, @usestockbrain, @rhokfun, @companypadfun, @HODLONROBIN, @delusional_rh, @Tulipcoin_RH, @kilncash, @brainonchain0, @locksleybank, @Source_Prtcl, @aresagentarena, @OrionisDeriv, @Blockmrkts)
    X accounts of the token projects themselves (search results or DEX Screener profile links of top pons-v2 pools), not personal KOL accounts.
  • @ponsrdotfun (tweet-to-launch bot)
    Bot deploys for requesters; its repo says the X-user-to-wallet map is private ("data/ and *.sqlite are ignored"). No public handle->wallet source.
  • fomo.family / fomopulse tracked traders (294 wallets)
    Public handle->wallet map (fomopulse /api/traders, config/wallets.json). TokenLaunched scan: not completed. Remaining wallets not scanned: RPC log queries with multi-address topics timed out or hit 429.