Futures Sniper

5 Year Derivatives Sniper. $ES. Macro Economics. Crypto. Trade Journal. Early Investor in asymmetrical bets.

[Futures Sniper @DayTradeKade]

"Don't be a hero. Don't have an ego. Always question yourself and your ability. Don't ever feel that you are very good. The second you do you are dead."
- Paul Tudor Jones

[Futures Sniper @DayTradeKade]

This one detail about $WALLET made me question the entire launch.

aa33 created it… but didn’t give itself any.

1 billion $WALLET were created.

Creator allocation: 0

Initial creator buy: 0 ETH

Essentially the entire supply went into the market/liquidity.

And that’s where this gets weird.

If this was just someone launching a Robinhood meme coin to make money…

why wouldn’t the creator keep a bag?

Especially when aa33 isn’t some random wallet.

Before $WALLET ever existed, we traced this same address through pre-public Robinhood Chain activity, Stock Token testing, ERC-8056 experiments, and wallets involved in the chain’s early infrastructure.

Then Robinhood Chain goes public.

9 days later, aa33 launches:

Robinhood Wallet ($WALLET).

And keeps none of it.

It makes me wonder if we’ve been looking at this backwards.

Maybe owning the token was never the point.

Maybe the goal was to get it into the market, distribute it, build liquidity…

and give it a purpose later.

Rewards? Fees? Wallet incentives? Access? Something we haven’t seen yet?

I still don’t know. But we will.

After everything we’ve uncovered around aa33, I have a hard time believing this was done for no reason.

If the creator didn’t create $WALLET to own it…

what the did they create it for?

[Futures Sniper @DayTradeKade]

29/ Why did THIS wallet launch $WALLET?

Not some wallet that showed up after Robinhood Chain became public.

This one.

A wallet whose history reaches backward toward people involved in building Robinhood Wallet…

then into Stock Token activity before its public significance…

then into Stock Token development itself…

and finally onto Robinhood Chain before public mainnet opened, funded by a wallet directly upstream of the chain’s rollup deployment.

I don’t know who was behind aa33.

But after tracing its history, I think figuring that out matters a hell of a lot more than the name of the token it eventually deployed.

30/ And there’s one final loose end.

Go back to where this investigation actually started.

The previous post wasn’t about $WALLET.

It was about the #1 $TIBBIR wallet and the strange network around it — the one we started questioning as a possible automated treasury or AI agent.

Somewhere inside that trail, $WALLET appeared.

That was the breadcrumb that sent us here.

Now we’ve followed it all the way back through Robinhood Wallet developers, pre-public Stock Token activity, and Robinhood Chain’s pre-public infrastructure.

So if the AI-agent theory from the previous investigation turns out to be right…

was $WALLET simply another token moving through the system?

Or was a potential AI agent leaving a breadcrumb for us to follow?

I don’t know.

But if it was a breadcrumb…

it led somewhere pretty damn interesting.

[Futures Sniper @DayTradeKade]

I told you there was another rabbit hole.

This is it.

$WALLET.

It started with that strange 333.3K transaction we found while digging through the #1 $TIBBIR wallet.

If you’ve been around the $TIBBER community, you already know why that made us stop.

333.3K.

It almost felt like another breadcrumb.

Maybe it was nothing.

But it was enough to make me open $WALLET and start tracing the wallet history behind it.

And that’s where this went somewhere I wasn’t expecting.

The further back I went, the closer the history got to Robinhood.

Not because of the token name.

Because of what the wallets had actually been doing.

The trail stretched back years — through people involved with building Robinhood Wallet, Stock Token activity before it was public, and eventually into Robinhood Chain before public mainnet even opened.

What started as another strange 333 breadcrumb turned into a much bigger paper trail.

Here’s what I found.

🧵👇

[Futures Sniper @DayTradeKade]

27/ And now we can throw away the thing that started all of this.

333.3K.

aa33.

Maybe those numbers meant something.

Maybe they meant absolutely nothing.

They did their job either way:

They made us look.

Because the case for taking aa33 seriously no longer depends on any of them.

It depends on transactions, timestamps, contracts and counterparties recorded years before $WALLET launched.

28/ So strip everything else away.

I can’t identify who controlled aa33.

I can’t say Robinhood authorized $WALLET.

But I also don’t think the history we uncovered fits neatly into:

“random wallet launches Robinhood meme coin.”

The same deployer sits at the end of a trail touching three separate eras of Robinhood’s Web3 buildout:

Robinhood Wallet.

Stock Tokens.

Robinhood Chain.

That is as far as the evidence takes me.

And it leaves one hell of a question.

[Futures Sniper @DayTradeKade]

25/ Now we have to put the strongest counterpoint on the table.

After Vlad Tenev’s X account was compromised in July and used to promote a fake memecoin, Vlad regained control and publicly said:

“Robinhood has not issued any coins or tokens.”

So I’m not calling $WALLET an official Robinhood token.

And I’m not claiming Robinhood authorized its launch.

That isn’t what this investigation established.

26/ What it established is a much stranger question.

How did the wallet that eventually deployed $WALLET end up with THIS history before the token existed?

A wallet can have genuine development provenance without every later action being an official corporate action.

aa33 could have been used by a developer, contractor, infrastructure partner, shared development operation, or someone else around Robinhood’s Web3 buildout.

It could also have changed hands or purpose over time.

We don’t know.

But now we know the mystery isn’t the token name.

It’s the deployer.

[Futures Sniper @DayTradeKade]

23/ July 10, 2026.

Nine days after public mainnet:

aa33 launches $WALLET.

And ironically, the launch itself might be the least interesting part of this investigation.

Anyone could deploy a token called Robinhood Wallet after the chain became permissionless.

But not everyone deploying one on July 10 has aa33’s history.

The token name made us curious.

The deployer’s history is the story.

24/ The launch adds one more detail.

The reviewed launch created:

1 BILLION $WALLET

and recorded:

initialBuyAmount = 0

We also don’t see aa33 simply allocating itself a massive creator balance at launch.

So this doesn’t resemble the most obvious version of:

copy a corporate name → mint a giant founder bag → dump.

Interesting.

But by this point, I cared far more about what happened before launch than the launch itself.

[Futures Sniper @DayTradeKade]

21/ Look at where tracing one deployer has taken us.

2022:

A funding wallet with history involving people building Robinhood Wallet.

2025:

aa33 funds a future Stock Token demo address before its public significance.

2026:

aa33 deploys and tests a Stock Token contract itself.

Then:

aa33 appears on Robinhood Chain’s pre-public mainnet, funded by a wallet directly upstream of the chain-deployment process.

And $WALLET still hasn’t launched.

22/ July 1, 2026.

Robinhood officially opens the public mainnet of Robinhood Chain.

This date changes the meaning of everything after it.

From here forward:

Anyone can access the chain.

Anyone can build.

Anyone can deploy.

Which is exactly why what aa33 did BEFORE July 1 is the part I care about.

[Futures Sniper @DayTradeKade]

19/ May 15.

The SAME F718 wallet funds:

aa33.

On Robinhood mainnet.

Now put the chronology together:

April 30:

F718 funds c845.

Six minutes later:

c845 executes Create Rollup.

May 15:

F718 funds aa33 on pre-public Robinhood mainnet.

July 1:

Robinhood opens public mainnet.

July 10:

aa33 launches $WALLET.

This is where the trail stops being about an old connection to Robinhood Wallet developers.

aa33 is now inside Robinhood Chain’s pre-public environment.

20/ F718 also provisioned multiple addresses during Robinhood Chain’s early period.

That gives its activity more context.

It wasn’t simply a wallet that appeared once to fund aa33.

It was distributing funds across the early network.

That looks much more like operational provisioning.

And aa33 was one of the addresses receiving it before the public was invited onto mainnet.

[Futures Sniper @DayTradeKade]

17/ April 30, 2026.

F718 funds:

0xc8451c5DE260E7ea1b879e7994967077e71230Ca

Wallet D — c845.

First:

0.00001 ETH.

Then at:

16:45:59 UTC

another:

0.2 ETH.

That second transfer becomes significant almost immediately.

Because Wallet D waits six minutes…

and then executes one of the most important transactions in this entire trail.

18/ 16:51:59 UTC.

Wallet D executes:

CREATE ROLLUP

TX:

0x7982d3d9da29185af78f7802cd2bdb04bdfb702766bb583c3b2804d762dc1fa8

That transaction created core rollup contracts underlying Robinhood Chain:

Rollup.

Sequencer Inbox.

Delayed Inbox.

Bridge infrastructure.

F718 had supplied ETH to the wallet just six minutes before it executed the transaction used to bring core Robinhood Chain infrastructure online.

Now jump forward two weeks.

[Futures Sniper @DayTradeKade]

15/ Before the next transaction, one distinction is critical.

Robinhood Chain:

MAINNET — 4663

TESTNET — 46630

Testnet was publicly accessible.

Finding aa33 there wouldn’t be especially interesting.

But the next activity wasn’t on testnet.

It happened on the actual Robinhood Chain mainnet before that mainnet was public.

16/ May 15, 2026.

aa33 receives:

0.15 ETH

from:

0xF718d37dBC25799f7cFf04B5AacdA94e87619649

Wallet C — F718.

Network:

Robinhood Chain MAINNET — 4663

Around block:

1,009.

Robinhood wouldn’t open public mainnet until:

July 1.

The future $WALLET deployer was already funded on the real chain roughly six weeks before public access.

That made the sender extremely important.

So we traced F718.

[Futures Sniper @DayTradeKade]

13/ There are only three transactions:

Mint.

Set UI Multiplier.

Set UI Multiplier again.

The multiplier calls happen just:

144 seconds apart.

First:

2

Then:

2e18.

It looks like a developer testing a value and then changing how that value is represented.

That specific function sent us into Robinhood’s Stock Token documentation.

14/ Robinhood’s documentation describes its Stock Tokens using:

ERC-8056 uiMultiplier()

The multiplier allows tokenized stocks to account for events such as stock splits without altering the holder’s raw onchain balance.

Now aa33 wasn’t simply near a future Stock Token demo address.

It had deployed and tested a Stock Token accounting mechanism relevant to Robinhood’s own architecture.

Robinhood Wallet had led us to Stock Tokens.

Stock Tokens were about to lead us somewhere even closer:

Robinhood Chain itself.

[Futures Sniper @DayTradeKade]

11/ At this point we had two different periods.

2022:

Wallet B has funding history involving Robinhood Wallet developers.

2025:

aa33 funds an address before it becomes publicly significant in Robinhood’s Stock Token demonstration.

Then in 2026, something changes.

aa33 stops merely interacting with Stock Token-related wallets.

It starts developing one itself.

12/ April 9, 2026.

aa33 deploys on Base:

0xE27e6C3ecF5315b1089f162709Dde34b9d49e9c7

Contract:

TestERC8056Token

Token:

Test Stock Token — tSTOCK

BaseScan identifies aa33 as the contract creator.

This time the connection isn’t another wallet aa33 happened to fund.

The future $WALLET deployer itself is now doing Stock Token development.

And the contract history shows it actively testing the mechanism.

[Futures Sniper @DayTradeKade]

9/ June 12, 2025.

aa33 sends:

0.000075391093466737 ETH

on Arbitrum to:

0x42607B2E4fde22e83822d4a86ddAc58d847DC289

At the time, that recipient had no obvious public significance.

Nothing about the transaction would have stood out.

Until 18 days later.

10/ June 30, 2025.

That recipient appears in the public OpenAI Stock Token demonstration associated with Robinhood and later highlighted by Vlad Tenev.

aa33 had funded it:

18 DAYS BEFORE.

That timestamp is what caught my attention.

Once an address becomes public, anyone can interact with it.

aa33’s interaction was already sitting onchain before the public had a reason to know that address mattered.

Our trail had just moved from Robinhood Wallet…

to Robinhood Stock Tokens.

[Futures Sniper @DayTradeKade]

7/ December 16, 2024.

Wallet B sends ETH directly to:

aa33.

On Arbitrum.

TX:

0x3d8399c33aa23977a45f5b6ba9c6e8c64f470ae6d3ec87ab3a905f0016b3a436

Amount:

0.000002463505845444 ETH.

The amount is tiny.

The history behind the sender is not.

This is the earliest direct inbound funding into aa33 we’ve been able to identify and verify in its reconstructed multichain history.

8/ This is where the timeline started bothering me.

That transaction happened in:

December 2024.

$WALLET wouldn’t exist for another year and a half.

Nobody was chasing the token.

Nobody had a $WALLET deployer to manufacture a connection to.

Yet the future deployer was already receiving funds from a wallet whose history ran through people involved with building Robinhood Wallet.

If that had been the only connection, maybe the trail ends there.

It didn’t.

Because the next time aa33 appeared somewhere interesting, it was connected to a Robinhood product that hadn’t been revealed yet.

[Futures Sniper @DayTradeKade]

5/ May 17, 2022.

Robinhood announces its standalone, multichain, non-custodial Web3 wallet.

When Robinhood Wallet entered beta later that year, the first blockchain it supported was:

Polygon.

So Wallet B was being provisioned on Polygon by an address carrying a Robinhood developer’s ENS identity 12 days before Robinhood publicly announced the product.

That was interesting on its own.

Then we checked Wallet B on Ethereum.

And found another Robinhood Wallet engineer.

6/ On Ethereum, Wallet B’s first funding came from:

richiereitz.eth

0x31C4e4e3C8214011363bAd98F0EE9C46CFD55091

Etherscan identifies Wallet B as:

“Funded By richiereitz.eth”

Richard Reitzfeld.

And Richard wasn’t just another Robinhood employee.

His public work history says he:

“Built and shipped Robinhood’s second iOS app, Robinhood Wallet from 0-1.”

His work included secure seed backup, non-custodial authentication, cross-chain swaps and expanding Robinhood Wallet from one blockchain to multiple chains.

Now look at Wallet B again.

On Polygon, its early funding traces to joshuajiang.eth.

On Ethereum, its initial funding traces to richiereitz.eth.

Two different chains.

Two people connected to building Robinhood Wallet.

Same wallet.

And we already knew where that wallet eventually sent funds.

[Futures Sniper @DayTradeKade]

3/ May 5, 2022.

joshuajiang.eth sends:

5 MATIC

to Wallet B.

Seven days later:

another 30 MATIC.

The May 5 transfer appears to be Wallet B’s first Polygon transaction.

The ENS had already been registered and reverse-resolved months earlier.

This looked less like a random interaction and more like early provisioning.

So the obvious next question was:

Who is Joshua Jiang?

4/ Joshua Jiang was a Robinhood developer.

Public source-code history includes work authored as:

Joshua Jiang
[email protected]

But the date is what made this interesting.

His address funds Wallet B on Polygon:

May 5, 2022.

Then, just 12 days later, Robinhood announces something directly related to what Joshua was working around.

[Futures Sniper @DayTradeKade]

1/ Start with $WALLET.

Token:

Robinhood Wallet

Ticker:

$WALLET

Contract:

0x0339f5459FC690aC85F1782e15782A151b4A9E1b

Deployer:

0x542718C390Ef1E4bEB46ce2023FfaA627db8aa33

Wallet A — aa33.

The name caught our attention.

But anyone can name a token anything.

If there was actually something here, it had to be in the deployer’s history.

So we started going backward.

2/ The earliest direct funding into aa33 we’ve been able to identify leads to:

0xf1a726210550c306A9964b251CBcd3fA5ecb275D

Wallet B — f1a726.

At first glance, there’s nothing remarkable about it.

But aa33 doesn’t begin with $WALLET.

Its trail leads backward into this wallet.

So before going any further with aa33, we needed to figure out where Wallet B came from.

[Not Telling @nottellingyou73]

@DayTradeKade Holy shit now this post from @DefinitiveFi makes sense!! You cracked the code!

https://t.co/VqfqQ2Srxn

[Futures Sniper @DayTradeKade]

21/ Maybe Wallet A is simply an extremely sophisticated whale.

Maybe it’s an automated treasury.

Maybe there’s an agent somewhere above this infrastructure.

I don’t know yet.

But there’s one question I keep coming back to.

This entire investigation started because $WALLET appeared in a transaction path that didn’t make sense at first.

And once I followed it, it exposed everything you just read.

So if Wallet A really is part of an autonomous system…

was $WALLET just another token moving through the machinery?

Or was the agent leaving a breadcrumb?

Because after finishing this investigation, I went back and traced $WALLET itself.

Who deployed it.

Who funded the deployer.

Where those wallets came from.

And what they were doing before $WALLET even existed.

That’s the next investigation.

[Futures Sniper @DayTradeKade]

I thought the #1 $TIBBIR wallet was just a whale.

36.6M TIBBIR sitting in one address.

Then I found one transaction I couldn’t explain.

$WALLET.

At first, it looked simple: another wallet had sent $WALLET to the main TIBBIR wallet.

But when I opened the sending wallet, the transaction told a different story.

It had actually sent $WALLET to a third wallet first.

So I followed that third wallet.

I expected to find another trader.

I didn’t.

What I found changed the way I look at the #1 TIBBIR wallet entirely — and eventually led back to a name this community knows very well.

Here’s the trail.

🧵👇

[Futures Sniper @DayTradeKade]

19/ I can’t prove Wallet A is controlled by an AI agent.

That’s where the evidence ends and my theory begins.

It could be a sophisticated trader, fund, market maker, bot operation, automated treasury, or some combination of those.

But I don’t think “random whale” explains the surrounding infrastructure very well anymore.

20/ For anyone who wants to trace the wallets themselves:

Wallet A — B433
#1 identifiable TIBBIR holder

0xb43341d20df16c11f8b390dc1a9131a353d75f5e

Wallet B — 3C77

0x3c7744d4d544c276b6a80013d9787a148b320ddf

Wallet C — A2FE
Definitive-linked

0xa2fe8e38a14cf7beece22ae71e951f78ce233643

Definitive Trading Vault Factory

0xdeF00000cc0a125ba7962e8113d3B69786851736

$WALLET

0x0339f5459fc690ac85f1782e15782a151b4a9e1b

base:0xa4a2e2ca3fbfe21aed83471d28b6f65a233c6e00

$TIBBIR