TIBBIR Universe 路 Saved post receipt 路 2092454308461842880
Kyle Chass茅 馃惛
@Kylechasse 路 Published: Wed Aug 26 03:29:17 +0000 2026
Original post on X 路 Full data receipt 路 Backup index
Saved archive render, not a screenshot of the original X page. Full captured content is retained below; capture gaps are stated explicitly. Video files are not stored.
UPDATE: The $TIBBIR wallet story just escalated.
We posted the short version earlier. Here's the full story.
The original wallet had been buying $TIBBIR every 30 seconds for six straight days after receiving $250K from Binance.
Then yesterday:
19:52 UTC: it stops.
19:56 UTC: a different wallet, funded with $80K from OKX, starts.
Same token. Same routers. Same 30-second rhythm.
3陆 minutes apart.
30+ hours later, the new wallet is STILL buying.
3,500 buys.
254K $TIBBIR accumulated.
75% of the $80K deployed.
Then something even more interesting happened.
01:58 UTC: the original wallet wakes up after 30 hours of silence.
One transaction.
It sends its entire remaining $350K to the SAME parent wallet that consolidated the 10M $TIBBIR last week.
That $350K is sitting there right now.
And within a minute, scammers started spoofing the wallet with fake $0 transfers from a lookalike address.
They're watching too.
Can I prove both wallets belong to the same operator?
No.
But Binance-funded wallet stops.
OKX-funded wallet starts 3陆 minutes later.
Then the original wallet sends its remaining $350K to the same parent.
The timestamps are on-chain.
Now I'm watching two things:
Where does the parent send the $350K?
And where does the new wallet send its 254K $TIBBIR?
If either touches the other cluster, we may finally have the link.

Image source: https://pbs.twimg.com/media/HQnj2Q-bsAA4Ynz.jpg?name=orig

Image source: https://pbs.twimg.com/media/HQnj2QyagAAmyCB.jpg?name=orig

Image source: https://pbs.twimg.com/media/HQnj-NObUAAeMkq.png?name=orig

Image source: https://pbs.twimg.com/profile_images/1980635945373167616/vpAh4t2B_200x200.jpg
Posts that embed this post
Provenance and integrity
{
"path": "sources/community-deep-dive-2026-10-14/fx-2092454308461842880.json",
"sha256": "6c34c14da91bc0fa8a0605bb91685b8f8a809377fd485d9d3a6c8c88025d3b1e",
"retrieved_at": null
}Receipt generated: 2026-10-15T09:54:54.418697+00:00. Publication and retrieval dates are separate. SHA-256 hashes detect changes; they do not independently authenticate the publisher.