Public registry · on-chain
KOL blacklist
Every wallet here is blocked from buying or receiving any token launched on this site until it bonds, enforced on-chain by the token itself. At the bond the token moves to Meteora and the block ends. The list is read live from the registry program.
- Listed KOL
- …
- Funded by a listed wallet
- …
- Proxy for a listed wallet
- …
- Manual decision
- …
Check a wallet
Reads the registry on-chain: listed or not, why, and X verification.
How a wallet gets listed
- 1Listed KOL. Known KOL wallets from public trackers, each checked on mainnet first.
- 2Funded by a listed wallet. A fresh wallet whose very first SOL came from a listed one, caught by the trace worker.
- 3Proxy for a listed wallet. A wallet shown to buy on a KOL's behalf, listed with evidence.
- 4Manual decision. Anything less clear goes to review with evidence, so nobody can get you listed by sending you dust.
What this stops, and what it can't
- Stopped:A listed wallet buys before the bond. The token's transfer hook rejects the buy, so the whole transaction fails and no SOL moves.
- Stopped:Someone sends tokens to a listed wallet. Rejected by the transfer hook on every transfer, on any app or DEX.
- Stopped:A listed wallet funds a fresh wallet directly. The trace worker lists the fresh wallet automatically (2 hops, first funding only).
- Not stopped:A listed wallet sells tokens it held from before. Allowed on purpose. Blocking sells would make every token a honeypot.
- Not stopped:A KOL uses a fresh wallet funded from an exchange. Can't be linked on-chain. The X-verified badge shows which buyers proved a real, non-KOL X account.
- Not stopped:A KOL buys through someone else's wallet. Not detectable on-chain. Reported proxies can be listed manually with evidence.
- Not stopped:A listed wallet buys after the bond. Allowed: the hook is switched off when the token moves to Meteora DAMM v2.