Crypto Pooky

I build systems that detect pre-listing signals in crypto. Currently shipping a listings intel engine in public. Alpha ≠ predictions. It’s early visibility.

[Crypto Pooky @CryptoPooky]

🧪 Build log #1

I’m building a system that detects exchange listing prep before announcements.

This feed =
• real catches
• real misses
• fixes in progress

No promises. No hype.
Just shipping + receipts.

#Crypto #OnChain #Web3

[Crypto Pooky @CryptoPooky]

Missed a few days of posting because I've been in the data trenches — cleaning up how our token catalog distinguishes between projects that share tickers. Boring, necessary work.

What surfaced inside the cleanup: an industrial token-impersonator factory on #Avalanche.
Thousands of fake contracts of well-known projects, byte-identical signatures, single coordinated actor.

The good intel hides inside the boring work.

#BuildInPublic #OnChain #DataScience

[Crypto Pooky @CryptoPooky]

Spent most of today debugging one of the hardest parts of this system:

token identity.

And it’s still a work in progress.

The data corruption has been stopped.
Cleanup is ongoing.

Detecting exchange-linked transfers is the easy part.

The hard part is:

• overlapping tickers
• different exchange naming conventions
• multi-chain deployments
• scam copycats
• recycled symbols
• inconsistent metadata

One small leak in entity resolution quietly snowballs into incorrect relationships across the DB.

Crypto data is way messier than it looks from the outside.

#buildinpublic #startuplife #crypto #onchain

[Crypto Pooky @CryptoPooky]

@KimVanLuu142080 It already landed on Bitget — this thread was actually a retrospective on the staging activity before the confirmation 👀

[Crypto Pooky @CryptoPooky]

$NEX -> #Bitget after 48 hours of trading
This is exactly why I like multi-exchange staging signals.

One exchange confirms first…

but sometimes the interesting part isn’t the first listing — it’s the trail left before it.

#KuCoin + #Kraken + #Coinbase activity was already sitting there in the data 👀

#prelisting #onchain #crypto #cryptoalpha

[Prelisted @prelisted_io]

🔄 48H UPDATE: $NEX on #Bitget

Signal detected May 21st: ~19.8h early 🛰️

Performance after 48h:
📈 +79%

Initial staging wasn’t isolated either:

• #KuCoin → $1.1B
• #Kraken → $619K
• #Coinbase → $347K

Interesting part: Bitget confirmed first, but the original activity was broader.

Watching whether additional venues resolve later.

#crypto #onchain #prelisting #cryptoalpha

[Crypto Pooky @CryptoPooky]

@TakashimaTakuji Yeah, the sequencing itself is becoming one of the more interesting signals to track 👀

[Crypto Pooky @CryptoPooky]

@BPeters2K4 Exactly.
Sometimes the first confirmation is just the visible endpoint.
The more interesting part is the coordination happening before the public announcement.

[Crypto Pooky @CryptoPooky]

Most people look for #listing announcements.

The edge is spotting the infrastructure behavior BEFORE announcements.

Dust txs.
Exchange wallet touches.
Routing tests.
MM staging.

The trick is filtering:
real prep vs fake exchange-bait noise.

$ZIK is interesting because the pattern doesn’t look fully organic yet — but it’s still too early for confirmation.

Exactly the kind of gray-zone signal we’re trying to refine at CryptoPooky 👀🐇
#crypto #CryptoAlpha #onchain #buildinpublic

[Prelisted @prelisted_io]

$ZIK is showing one of the more interesting early-stage patterns we’ve seen lately.

Not “confirmed listing” activity.

But possible infrastructure prep.

Over the last few days, wallets tagged to:
#Binance, #OKX, #KuCoin, #Kraken, #Coinbase, #HTX, #Bitfinex and others
have all interacted with the token in small repeated transactions.

Most transfers are tiny “dust” amounts — which is exactly what often appears during:
• address testing
• routing validation
• MM prep
• exchange compatibility checks

Important:
This does NOT mean a listing is confirmed.

But multi-exchange wallet touching in a compressed timeframe is not typical random retail behavior either.

Right now this looks more like:
Stage 1–2 wallet staging
than actual exchange deployment.

Watching for:
• repeated reuse of the same exchange wallets
• larger follow-up transfers
• liquidity expansion
• market maker overlap

That’s where signal quality increases dramatically.
#crypto #cryptoalpha #onchain

[Crypto Pooky @CryptoPooky]

Funny update on this one:

Yesterday I was saying “the interesting part isn’t where, it’s the coordinated movement itself.”

Today $CTR:

🟢 #Coinbase confirmed
🟢 #Kraken confirmed
🟢 #HTX confirmed

#MEXC landed first, but the footprints were already scattered across the ecosystem.

Exchange listings often behave more like dominoes 👀
#crypto #listing #onchain

[Prelisted @prelisted_io]

Update:

Since initial confirmation $CTR got listed on:

🟢 #Coinbase → ~24.7d lead
🟢 #Kraken → ~15.0d lead
🟢 #HTX → ~35.3h lead

Initial staging activity was appearing across these venues before the first public listing landed.

Interesting footprint 👀
#crypto #onchain #cryptoalpha

[Crypto Pooky @CryptoPooky]

Spent today digging into one of those bugs that looks obvious only after you find it 😂

I had 3 different tokens called $SLX sitting in the DB.

#MEXC listed one of them.

The matcher confidently picked… the wrong one.

Which is funny because I kept thinking:

“Wait, why does this footprint feel weird?”

Turns out I was still letting ticker symbols leak into project identity.

Tickers feel reliable until you run into multi-chain deployments, copycats, or projects reusing symbols.

Then suddenly you’re basically flipping a coin.

Shipped the fix:

Reinforced picking contracts first, tickers second.

Tracker rabbit hole #284 🐇

#buildinpublic #crypto #onchain

[Prelisted @prelisted_io]

Interesting edge case surfaced this week:

Three completely different tokens sharing the same ticker: $SLX

• Slimex - BNB Chain (SLIMEX/USDT on MEXC)
• Solstice - Solana (listed on MEXC as SLX/USDT)
• A BNB copycat (0x70db0c…) with no CoinGecko identity

What happened:

When #MEXC listed Solstice, our confirmation pipeline matched the event against previously detected on-chain activity.

Problem: those signals actually belonged to the BNB copycat.

Subscribers briefly received an incorrect confirmation (~2d lead, 5 signals caught).

Root cause - ticker collisions.

Contract-level attribution was always preferred, but reliable exchange-side contract data wasn’t consistently available in the pipeline.

Today I patched pulling network contract mappings directly from exchange metadata across multiple venues, which allowed replacing ticker-first matching with contract-first resolution.

Fix shipped.

Incorrect confirmation removed from audit history and a correction sent to subscribers.

Reminder:

Names can collide. Contracts generally don’t.
#crypto #onchain #web3

[Crypto Pooky @CryptoPooky]

I keep noticing while reviewing older detections: signals mostly don’t resolve in one event.

$UNITED started as a noisy-looking April footprint with very low confidence.

54 days later:

#MEXC → #HTX → #Gate → #KuCoin → #Bitget

The interesting part isn’t “predicting one exchange.”

It’s catching the footprint before exchanges start moving.
#crypto #onchain

[Prelisted @prelisted_io]

🚨 CONFIRMATION: $UNITED → #Bitget

Signal detected: Apr 1
Lead time: 54 days
Signal footprint: 6 on-chain signals

Initial activity wasn’t isolated:
After the original detection, $UNITED later listed across multiple venues:

• #MEXC (May 10)
• #HTX (May 10–12)
• #Gateio (May 10–12)
• #KuCoin (later delisted May 22)
• #Bitget confirmed today

Sometimes the signal resolves as one listing.
Sometimes it turns into an exchange trail.
#crypto #onchain #cryptoalpha

[Crypto Pooky @CryptoPooky]

Just pushed a fix.

Binance US was sharing attribution with Binance Global in some cases, which could create noisy staging detections.

Split Binance US into its own exchange and re-mapped ~82 wallets, so this class of false positives should be filtered now 😄

Appreciate the bug report 🐰

[Crypto Pooky @CryptoPooky]

One thing I’m noticing while reviewing older catches:

The strongest signals often don’t look exciting at first.

$TRAC sat there for weeks.

Small activity → repeated signals → eventual routing → confirmation → +110% 48h move.

The pattern matters more than the individual transaction 👀
#Upbit #crypto #onchain

[Prelisted @prelisted_io]

🔄 RETROSPECTIVE: $TRAC → #Upbit

Detected: Apr 1
Confirmed: May 18
Lead time: 46.3 days 🛰️

Signal footprint:

• 9 on-chain signals
• repeated activity over ~3 weeks
• eventual Upbit routing

48h after listing:
📈 +110%

Interesting part:

This wasn’t a single wallet move.

The pattern formed gradually before resolving into a real listing.

#onchain #crypto #prelisting

[Crypto Pooky @CryptoPooky]

This is one of the patterns i often notice:

The exchange showing the earliest activity isn’t always the exchange that confirms first.

$CTR was leaving footprints across #Coinbase + #Kraken + #HTX…

Then #MEXC landed first.

Makes me think the interesting signal isn’t “where” — it’s the coordinated movement itself.
#crypto #cryptoalpha #onchain

[Prelisted @prelisted_io]

🚨 CONFIRMATION: $CTR → #MEXC

Interesting one:

Initial staging footprint wasn’t on MEXC.

Detected activity was appearing across:

• #Coinbase
• #Kraken
• #HTX

MEXC ended up confirming first.

This is why the footprint is more important than the specific venue — exchange prep often spreads before the first public listing lands 👀
#crypto #cryptoalpha #onchain

[Crypto Pooky @CryptoPooky]

Nice catch — I looked into it.

TRAC isn’t behaving like a typical pre-listing footprint.

TRAC is already listed on Binance US, and ~95% of these transfers are hitting a Binance US hot wallet, so that activity is likely just regular user flow. The remaining ~5% appears to be routing mirrors, which aren’t high-value signals.

So this specific case looks like signal noise rather than genuine staging.

These are exactly the weird edge cases that help improve the tracker 😄 Appreciate you pointing it out — already on it.

[Crypto Pooky @CryptoPooky]

Interesting discussion here 👇

Execution matters, but this is the pattern I noticed while reviewing catches:

The strongest moves often happen when it’s either:
• first-ever exchange exposure
• or major exchange events (#Binance / #Coinbase / #OKX etc.)

Been tracking post-listing behavior on recent detections, small sample below👀
#crypto #onchain

[HaasOnline @haasonline]

@CryptoPooky For real. Most traders see it on one exchange and it's already spreading to the rest. When you can execute across all those venues simultaneously though, that's the real edge.

[Crypto Pooky @CryptoPooky]

True, execution speed becomes the edge once the event is public.

I’m mostly focused on the earlier part: finding the footprint before the event resolves.

Also noticed something while reviewing catches: the strongest performers are often either:
- first-ever exchange listings
- or top-tier listings (#Binance / #Coinbase / #OKX etc.)

I put recent detections on https://t.co/RgezI4qTZv if you’re curious - the last ~20 catches give a decent picture of lead times and post-listing behavior 👀

[Crypto Pooky @CryptoPooky]

Strange #MEXC blip today: token $AMA appeared in their currencies API at 07:40 UTC, gone by 08:10. Zero trading pairs the whole time.

Pre-listing prep? Internal test? Hard to say — but exchange data is messier than people think. One API snapshot ≠ truth, but still worth noting.

#crypto #buildinpublic

[Crypto Pooky @CryptoPooky]

Well this aged nicely 😂

Caught it → posted it → forgot about it → now $GENIUS -> #Binance confirmed ~41 days later.

Receipts matter.

Still one of my favorite things about tracking exchange staging:
sometimes tiny weird signals end up being the real story 👀
#crypto #onchain #cryptoalpha #prelisting

[Crypto Pooky @CryptoPooky]

Caught this earlier today 👇

$GENIUS → #Bitget

🕒 6.8h before official listing

Didn’t post it live (traveling), but this is exactly the type of signal the tracker is built for.

Early staging → listing confirmation.
#crypto #alpha #onchain

[Crypto Pooky @CryptoPooky]

Hmm 👀

Guys, does anyone actually know what’s happening with $ZIK?

Seeing repeated activity across a bunch of exchanges, but the project itself feels weirdly quiet.

Multiple days of movement usually isn’t random.

Curious if anyone has deeper context.
#onchain

[Prelisted @prelisted_io]

📡 WATCHLIST: $ZIK showing unusual multi-exchange staging activity

Activity detected across:
• #OKX
• #Binance
• #Coinbase
• #KuCoin
• #Kraken
• #HTX
• + more

Repeated transfer clusters over multiple days, but still no confirmed listing event.

Interesting part: broad exchange activity + very limited project visibility.

Watching this one 👀

#onchain #crypto #prelisting #cryptoalpha

[Crypto Pooky @CryptoPooky]

Another one from the pipeline 👀

$UP (Superform) → confirmed on #Bitget

• 5 on-chain signals
• ~7.3h lead time
• No CoinGecko ID at detection

Interesting thing about early signals: they often look incomplete when you catch them.
No market page. No hype. No obvious “announcement”.

Just flows.

Then later they resolve into something real.
#crypto #onchain #web3