Яocketdoc

$TIBBIR $ALTT
HOOD is the future
Ribbit hole
Altcoinist bot maxi

[Яocketdoc @rocketdoc_eth]

Not sure why they didn't link the site on X.

The token tells you where it is.

https://t.co/eTCvwPYHLv

[Revvy @tryrevvy]

Revvy is LIVE on @base.

A launchpad that turns trading fees into programmable value. Powered by @clanker_world.

Every coin has a different purpose. Its fees should work that way too.

Choose Programs at launch to decide how a share of your coin’s trading fees gets put to work. Different rules, different outcomes, built around your community.

Give holders a reason to participate. Fund what your community needs. Create value beyond launch.

Your coin. Your programs. Your fee flow.

CA: 0x3441e8fCdD380c4e7F5C7F55CCd599B2a2afCcCC

[Яocketdoc @rocketdoc_eth]

I have no expectations and therefore can never be disappointed, only pleasantly surprised.

[Яocketdoc @rocketdoc_eth]

@Altcoinist @davidsenra

[Bunny Open Studio @officialbunnyos]

Introducing Bunny Open Studio - The AI studio for character IP.

Characters are the bedrock of memecoin culture. Communities rally around them, create memes and bring them into the spotlight. Some grow into standalone IPs, with toys, plushies, content and entire worlds built around them.

Bunny Open Studio brings that journey onto one platform: launch tokens backed by character IP, create content with AI and distribute it at scale on X.

We’re introducing the Open Character Token Standard (OCT), a proposed standard where teams pledge to transfer their character IP to a Cayman SPC, with governance structured to let token holders collectively shape its future. The goal is to give communities a stake in the characters they help build.

Over the past 11 months, we’ve built in public across DeFi, inference infrastructure, AI content generation and even an MMORPG. Now, we’re bringing that experience together at the intersection of community, entertainment and finance.

The platform is in early beta, with updates shipping daily. Powered by @higgsfield, @sumelabs and our friends at @base and @AskVenice.

[Яocketdoc @rocketdoc_eth]

@Altcoinist 😂 still impressive shipping!!
$ALTT

[Яocketdoc @rocketdoc_eth]

@goon_crypto @fablesfi @bot Just the best returns. With the guardrails of not being exposed to volatile assets (ended up in cbbtc/usdg pool unsurprisingly)

[Яocketdoc @rocketdoc_eth]

@fablesfi Yep landed in my wallet 👍

[Яocketdoc @rocketdoc_eth]

@RealLousyLover @Keetaaahhh Because the bot says to

[ribbita @ribbita2012]

THE FUTURE IS HOOD.

TIBBIR was built for real world assets. The Robinhood Chain has built an incredible ecosystem for tokenized assets onchain. It is clear that for the TIBBIR community to take the leap into the real world, the time has come to 🌉

Gribbit.

https://t.co/DlqtJz6rnO

[Яocketdoc @rocketdoc_eth]

with https://t.co/FuYkXJ2T7g and api/screen being "unavailable", its essentially the same as the bridge being closed.

you can't use the basescan contract and write directly to it to bridge because openToAll() is false. there are allowlisted wallets apparently, but my wallet that could initially bridge gets on the Read Contract -> allowedAmount, and the value retuns as 0, essentially showing that my wallet isn't allowlisted.

So i could bridge because i passed api/screen. But now that api/screen is "unavailable", unless the opentoAll is activated to "true", you still need bridgeAuthorized, which is only given when you pass /api/screen.

So, hope you guys bridged while you could. i'm not calling it bullish or bearish that api/screen is unavailable, but the fact its been down more often then not in the past week is "interesting".

.@mickymalka .@RibbitCapital

[Яocketdoc @rocketdoc_eth]

Nice find.

Looking back it's burnt 103 tibbir since Oct 11.

I got my bot to dive and summarize

Teller Borrow n’ Burn - TIBBIR summary

What Teller is:

DeFi lend/borrow (https://t.co/frhLriQVWG, @useteller): borrow stables against crypto / tokenized stocks with fixed terms and no mid-loan margin calls. You repay or roll by the due date.

The loop (Borrow n’ Burn)

Someone borrows stables on Teller using an eligible token (e.g. TIBBIR) as collateral.

Part of the loan fee is used to buy that same collateral token on the market.

Those bought tokens are sent to the dead address (burned from circulating supply).

@BorrowBurnBot announces each burn; @useteller RTs them.

Official BnB executor (Robinhood Chain)
0x412BFb421899d9bA66F3A7390Fe9302cFb84FCb6
Gas-seeded by Teller ops 0x8cfd836b4fcd05414f63523bc02f24bda992aa20. Address not printed on https://t.co/uBGmXFO48o, but confirmed via bot announcements + useteller RTs + matching on-chain burns.

TIBBIR token (official RH ERC-20 — not the BnB wallet)
0x4db7374E966097be94C6680d49156D580F097Bbf
Dead address: 0x000000000000000000000000000000000000dEaD

This EOA’s TIBBIR burns

Total: 103.383790569056054457 TIBBIR across 12 transfer-to-dead txs

First: 2026-10-11 00:01:17 UTC / 11:01:17 AEDT — tx

Latest (Karl’s “~6.51”): 2026-11-06 00:02:12 UTC / 11:02:12 AEDT

That latest sequence (exact)

Buy — 2026-11-06 00:02:09 UTC / 11:02:09 AEDT · block 107144486
tx 0x84a3245eb19aeabe5ef7972ea225bc64783ce41b0108268cafe75b32ec97d576
EOA paid 1.157997 USDG (0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168) via https://t.co/I72SWgVfCS Diamond 0xB477751B76CF82d00a686A1232f5fCD772414Af3 → received 6.511590952754103633 TIBBIR (path USDG → NVDA → WETH → TIBBIR).

Burn — 2026-11-06 00:02:12 UTC / 11:02:12 AEDT · block 107144515 (~3s later)
tx 0x141fd5092289ba181aece6caba8c804a00b40fe88f87656f7dbbea8da44d16e5
Same EOA transfer’d the full 6.511590952754103633 TIBBIR to 0x000000000000000000000000000000000000dEaD.

[Karl Baker @bedigitalmedia]

My boy has been monitoring robinhood:0x4db7374e966097be94c6680d49156d580f097bbf

Teller’s Borrow n’ Burn account reported the first TIBBIR buyback and burn I’ve found on 6 November at 01:55 UK time: 6.51 TIBBIR, about $1.16, bought on the market and

[Яocketdoc @rocketdoc_eth]

@whatifwhyhow No I was saying that when api/screen goes down can't see why that happens.

And yes it's currently up and working

[Яocketdoc @rocketdoc_eth]

Can't get behind vercel to see where it's failing or what protocol specifically is being used by api/screen

/api/screen is a plain HTTPS GET that returns JSON. It's a Next.js server route on Vercel, running in the US East (iad1) region, and the page calls it with an ordinary fetch. Which screening service it calls behind that isn't visible from outside, because the call happens on the server. None of the known screening providers (GoPlus, Blockaid, Chainalysis, TRM and similar) appear anywhere in the site's code, so naming the failing upstream will need their server logs or source code.

[Яocketdoc @rocketdoc_eth]

@bagsOG707 😭 man $nox destroyed my faith in virtuals.

Lucky my $tibbir token was bridged to RH and is not part of that anymore

[Яocketdoc @rocketdoc_eth]

@specmacs @SpoliticusMedia Lmao 💯

[Яocketdoc @rocketdoc_eth]

@cunningreyfox @Keetaaahhh gentle prod to them that maybe its not indefinite?

[Яocketdoc @rocketdoc_eth]

@SpoliticusMedia haha, the grass feels good between my toes

[Яocketdoc @rocketdoc_eth]

I don't know, its an easy way to stop bridging if you're doing something back end... but don't want to call a change to the contracts which requires the multisig/owner stuff etc...

but yeah, bridge IS essentially closed while api/screen is unreachable except for allowlisted wallets (who knows who they are)

[Яocketdoc @rocketdoc_eth]

@moonpay

[Яocketdoc @rocketdoc_eth]

You know what's interesting, there were multiple other coins launched that listed the deployer wallet as their launch wallet. The launchpad had that function... All of those coins rugged.

There were 4 wallets that did this. I traced them.

How they were funded: each was funded on Robinhood Chain on 8 Jul through the Relay bridge, the same route lots of retail users take.

Different account type: they're plain wallets. The deployer is an Alchemy smart account funded directly by F718.

Why the deployer shows as creator: the launch factory lets whoever launches a token name any wallet as its creator. These four did that seven times. They also launched other tokens naming themselves, and one of them (0x83598fbd…c3a1) has launched more than 85 tokens. The deployer never signed any of those launches.

So the real "token family" is only $WALLET. The other seven look like copycats riding the story and pointing creator fees at the deployer, so they shouldn't count as evidence about who runs it.

One odd detail: four of those copycat launches came on 8 Jul, two days before $WALLET existed. That fits people who were already watching the deployer that day, when it made its $1 test buys.

Ppl had the deployer wallet on their radar. They front ran it with rugs. Then it launched $wallet

[Яocketdoc @rocketdoc_eth]

My grok bot looked through the $wallet onchain stuff.

Interesting take... Here's what it says.

The $WALLET deployer funded Vlad's demo wallet on 13 Jun 2025, about 17 days before the demo, so this happened before any leak. That reverses my earlier read. I now think the deployer is most likely run by someone in Robinhood's demo or engineering team, or on Vlad's behalf.

The funding (to demo wallet 0x42607b2e4fde22e83822d4a86ddac58d847dc289, Sydney time)

At 7:37am the issuer 0x44c7c4ab…c43 sent it 10 "Demo 1" and 10 "Demo 2" test tokens.

At 9:14am the deployer sent it 0.0000754 ETH for gas, tx 0x191c3f05…16c6. That's the demo wallet's first-ever ETH.

At 9:34am the deployer sent it 0.5431 ARB, tx 0xcca59058…a6.

About 20 minutes later the demo wallet started its Demo 2 test transfers. The live demo was around 1 Jul 2025, which lines up with Robinhood's Cannes event.

Nothing ever went back from the demo wallet to the deployer, on Arbitrum or Ethereum.

Why the leak doesn't explain it

Someone who learned the demo wallet's seed later could take over that wallet, but not the deployer. And the deployer topped it up 1.5 hours after it got its demo tokens, which looks like the demo operator getting it ready.

The deployer is also a long-lived wallet, active since June 2024. Separately, the demo wallet woke up suddenly on 12–13 Jul 2026. It bridged funds out, funded the wallet that bought $1, and pulled liquidity. That fits a hacker using the leaked seed and has nothing to do with the deployer.

Updated verdict

About 70% that the deployer is controlled by someone in Robinhood's demo or engineering team, or by someone operating wallets for Vlad.

About 20% that it's an official, sanctioned Robinhood stealth launch.

About 10% that it's an unrelated third party.

So this is an insider-linked launch, but it doesn't look corporate. It was a 0.0005 ETH launch on the public factory, the deployer never held or sold any WALLET or touched its fees, Robinhood has stayed silent for four months, and there's the unverified claim that Robinhood Wallet flags the address as "prohibited". That looks more like an employee's personal wallet launching a meme than a stealth Robinhood launch. That would also explain why Robinhood is keeping its distance.