Wishing you a great day
Joined April 2021
- Tweets3.3K
- Following3.2K
- Followers2.9K
- Likes2.6K
Pokadoi retweeted
ask glyph for allocation 💬🌊
type /glyphfree
askglyph.chat
Pokadoi retweeted
🚨 $WALLET just got a LOT more interesting.
I tested KuCoin Alpha’s Robinhood-chain routing directly — and the result is NOT just “last viewed token” behavior.
Here’s what happened:
MEME was explicitly saved as the active Robinhood Alpha token.
Then I opened a completely invalid Robinhood contract:
0x1111111111111111111111111111111111111111
KuCoin did NOT stay on MEME.
It automatically switched to:
$WALLET — 0x0339…9e1b
Then the HAR network capture showed the exact sequence:
invalid Robinhood token
→ initAlphaCurrency
→ validation request
→ lookup fails
→ innerJump
→ URL switches to $WALLET
→ KuCoin validates WALLET
→ WALLET loads
And here’s the crazy part 👀
KuCoin switches to WALLET BEFORE its normal Alpha token-list APIs are even fetched.
So this does NOT look like:
“fetch Robinhood tokens → WALLET happens to be first → display it”
It looks much closer to:
Robinhood Chain → preconfigured/default Alpha asset → $WALLET
Even more telling:
Solana invalid routes deterministically fall back to ALTSZN.
Robinhood invalid routes deterministically fall back to WALLET.
That strongly suggests KuCoin has a chain-level Alpha fallback system — and for Robinhood Chain, that fallback is specifically $WALLET.
This does NOT prove Robinhood issued the token.
But it DOES show KuCoin’s own trading terminal treats $WALLET as the deterministic/default destination for unresolved Robinhood-chain Alpha routes.
That is a very specific position to occupy. 👀🏹
Robinhood → WALLET
Keep digging.
Pokadoi retweeted
🧵 This investigation started somewhere I didn't expect:
In a court case.
While researching $WALLET, I came across Aspalathos Investments v. John Does 1–10.
The case identified an Ethereum address now publicly labeled:
0xf70d...dbEF = Relay: Solver
Circle was instructed, after communicating with Relay, to provide information about the wallet's function, ownership and control.
That changed my approach.
Instead of only following wallets, I started following the infrastructure:
Relay → settlement → USDG → Paxos → Robinhood Chain
That eventually led me to:
624c
1/
Before $WALLET existed, aa33 was already active inside Robinhood Chain's emerging infrastructure.
aa33 is important for one obvious reason:
It later deployed $WALLET.
But on May 20, aa33 appears at the beginning of 624c's observed Robinhood Chain history.
aa33 → 624c
This happened before 624c's later significance was visible.
And before $WALLET existed.
2/
Then F718 enters the picture.
F718 had already appeared throughout Robinhood Chain's early funding environment.
It later sends 624c a 3 ETH top up.
22m55s later, 624c begins funding Stock Token production role wallets.
Eventually:
624c → 12/13 observed production roles + grantor
624c was clearly becoming operationally significant.
3/
Now for the independent check.
SQD analyzed Robinhood Stock Token activity without starting from our $WALLET address graph.
Their data independently leads to the same 624c address.
The first TSLA Stock Token mint appears June 22.
On June 26, 624c appears in early TSLA/USDG flows, including a DvP transaction involving:
0.0129 TSLA ↔ 4.9575 USDG
4/
Later that evening:
0.01 TSLA → 624c
Tx:
0xc82f4251f3677088ddb2de26c2489087b7fbdd2ea345cc1dbb01dade9de67940
~8 minutes later, 624c sends exactly 0.01 TSLA onward.
SQD notes this may represent custody, settlement or operational rebalancing rather than a trade.
5/
Now put the two paths together.
PATH 1
aa33
↓
624c
↓
Stock Token production roles
PATH 2
Stock Token ledger
↓
TSLA / USDG
↓
624c
Two independent routes converge on the same address.
6/
And now the chronology:
May 20
aa33 → 624c
June 22
First TSLA Stock Token mint
June 22 onward
624c involved in production role provisioning
June 26
624c appears in TSLA/USDG flows
July 10
aa33 deploys $WALLET
$WALLET comes last.
7/
That's the key.
aa33 didn't deploy $WALLET and then create connections to interesting Robinhood addresses.
The connection existed first.
624c subsequently became embedded in Stock Token operations.
Only afterwards did aa33 deploy $WALLET.
8/
This does NOT prove Robinhood created $WALLET or controls aa33/624c.
But it makes the "random meme deployer manufacturing Robinhood connections afterwards" explanation much harder.
So maybe we've been asking the wrong question.
Not:
"Can $WALLET be connected to Robinhood?"
But:
"What was the future $WALLET deployer doing inside this infrastructure before $WALLET even existed?"
A court case led me to Relay.
Relay led into the infrastructure.
The infrastructure led to 624c.
And 624c led straight back to aa33.
Before $WALLET existed.
$WALLET #WALLET #Robinhood #RobinhoodChain
Pokadoi retweeted
📢#KuCoin Alpha has Listed Token: MEME and WALLET
🗓 Trading starts now
🔁 Pair: WALLET/USDT and MEME/USDT
🌐 Network: Robinhood Chain
Discover early stage innovation and start trading in the KuCoin Alpha Zone.
👉🏻 kucoin.com/announcement/en-k…
#KuCoinAlpha #WALLET #MEME
Pokadoi retweeted
I just figured it out
@JJcycles is Joshua Jiang (the guy who launched $WALLET and works at Robinhood, that’s why Robinhood just reposted his post)
See research here:
One of the more interesting trails around aa33—the wallet that launched $WALLET—is its connection to Joshua Jiang, a Robinhood engineer.
Public development history includes commits authored as Joshua Jiang <[email protected]>, while his GitHub profile has also associated him with @robinhoodmarkets.
Now look at the onchain trail.
In May 2022, joshuajiang.eth sent 5 MATIC and then 30 MATIC to f1a726.
Separately, another wallet appearing in Joshua/Robinhood development artifacts—0x1fB4...4f0A—later funded the exact same f1a726 wallet on Optimism.
Then, beginning in 2024, f1a726 developed a repeated multichain transaction relationship with aa33.
And in August 2025, aa33 acquired:
jj.staketr.hi
So:
Joshua-linked wallets → f1a726 → aa33 → jj.staketr.hi → $WALLET
His X profile even says he’s an engineer.
@JJcycles is the founder of $WALLET
$wallet With the release of the statement, the icons in the product have been updated (since rh has explicitly stated that official elements cannot be used or tampered with)🏹🏹🏹🚀
WALLET liquidity in a vault with AI management enabled.
WALLET delivered through signed intent orders.
WALLET quoted through an agent-facing swap interface.
All coincidences will turn into reasonable arrangements
🚨 $WALLET rabbit hole just got WILDER.
Back in June 2025, former Crossmint BD/GTM employee Alex Acuña cryptically posted:
“Follow the white rabbit 🐇
Follow the green frog 🐸
33”
Alex Acuña = AA
AA + 33 = aa33 👀
$WALLET deployer? 0x5427…aa33
Crossmint was backed by Ribbit Capital, a longtime Robinhood investor—and later became a Robinhood Wallet infrastructure partner.
And aa33 already has multiple pre-public Robinhood-linked breadcrumbs.
Coincidence? Maybe. But damn… 🐇🟢 nitter.cf/toorobravo/status/1938…
Pokadoi retweeted
🚨 $WALLET rabbit hole just got WILDER.
Back in June 2025, former Crossmint BD/GTM employee Alex Acuña cryptically posted:
“Follow the white rabbit 🐇
Follow the green frog 🐸
33”
Alex Acuña = AA
AA + 33 = aa33 👀
$WALLET deployer? 0x5427…aa33
Crossmint was backed by Ribbit Capital, a longtime Robinhood investor—and later became a Robinhood Wallet infrastructure partner.
And aa33 already has multiple pre-public Robinhood-linked breadcrumbs.
Coincidence? Maybe. But damn… 🐇🟢 nitter.cf/toorobravo/status/1938…
Pokadoi retweeted
🚨 $WALLET UPDATE — SOMETHING JUST CHANGED.
Remember the wallet previously labeled “@GATE” on @nansen_ai ?
The GATE label has now disappeared.
But the wallet didn’t disappear.
It bought more $WALLET.
Its position has now grown to approximately:
9.94 MILLION $WALLET 🪶
And here’s the part that matters:
those tokens were sent into liquidity pools. 💧
Think about the sequence:
GATE label appears → WALLET accumulation → label disappears → accumulation continues → ~9.94M WALLET → liquidity deployment.
At 1B total supply, 9.94M represents almost 1% of the entire supply.
This no longer looks interesting simply because somebody bought a large bag.
The real question is what the capital is being positioned FOR.
If those tokens are being deployed systematically into liquidity rather than simply held, we should be watching for:
deeper liquidity → tighter spreads → larger executable size → professional market making → exchange readiness → listings.
We’ve been talking about this exact transition.
The alpha may not be in watching the price.
THE ALPHA MAY BE IN WATCHING WHO IS BUILDING THE MARKET BEFORE EVERYONE ELSE ARRIVES.
Follow the liquidity.
Follow the infrastructure.
Follow the wallets.
🛡️ RAISE SHIELDS.
🪶 PASSWORD: $WALLET.
Pokadoi retweeted
The roads had been built. Now we wanted to know what happened when $WALLET started travelling on them. Read article V:
Pokadoi retweeted
We followed one wallet upstream and we found the infrastructure of an entire financial ecosystem. Read part IV: THE ADDRESS THAT HELPED BOOT A CHAIN....
$WALLET
Pokadoi retweeted
New $WALLET finding:
c845 wasn’t just a deployment wallet
Remember:
0xF718d37dBC25799f7cFf04B5AacdA94e87619649 (F718)
funded both:
0xc8451c5DE260E7ea1b879e7994967077e71230Ca (c845)
and
0x542718C390Ef1E4bEB46ce2023FfaA627db8aa33 → later launches WALLET.
Etherscan confirms c845 was funded by F718, and then shows c845 making direct Execute Call transactions to Robinhood Chain’s privileged UpgradeExecutor:
0x552603b4bc1f5E896AF2854548D6380f45f1B4bf
on April 30 and May 1.
Even more importantly, Robinhood Chain’s original createRollup transaction contains a decoded RoleGranted event on that UpgradeExecutor:
The event is a genuine AccessControl RoleGranted event—not just a permissionless transfer. The same deployment transaction also transferred ownership of the canonical ProxyAdmin to the UpgradeExecutor.
That matters a lot.
A random user can bridge through Robinhood Chain.
A random user can call WETH.
A random user cannot simply grant themselves an UpgradeExecutor role during the canonical rollup deployment.
It establishes that F718 funded an address which actually possessed privileged Robinhood Chain deployment authority.
TLDR:
The wallet that funded the $WALLET launch wallet also funded the wallet that had privileged Robinhood Chain deployment authority.
It’s clear as day every single wallet linked to the $WALLET launch wallet is either a known Robinhood employee or has deployment authority on Robinhood Chain
Stealth mode will have to end soon because we’re catching on @vladtenev 🔮
新台子的第一个币，官方承认的。
0x77061b45c5e4d440bd681b5f72bd0f4231a6fc04
nitter.cf/jakegallen/status/2092…
1/ Emblem Launchpad has expanded to Robinhood and @ponsdotfamily as the home.
Their team, adoption, and tooling provides the most confidence and durability to the standards that our community expects from us.
11 days ago, I deployed $ROBINVAULT to test this theory
Pokadoi retweeted
TL;DR on the new Mercury finding
aa33 was already operating inside Robinhood’s restricted pre-launch infrastructure.
We also know it deployed a test token whose verified source explicitly says it was for “Mercury ui_multiplier / ui_quantity integration.”
If you search for a token in Robinhood Wallet, the app calls Robinhood’s Mercury backend — for example:
api.robinhood.com/mercury/v3…
Mercury is the core backend/orchestration layer behind Robinhood Wallet’s token discovery, holdings, portfolio, swaps and transaction flows.
So aa33 wasn’t just provisioning infrastructure — it was directly involved in Robinhood Wallet integration/QA work.
nitter.cf/cult_of_carrion/status…
Pokadoi retweeted
What if $WALLET wasn’t a random token at all — but the final piece of a programmable wallet architecture that was already being built in plain sight?
Follow the wallets, the permissions, the pre-release tests, and the money. 🧵
futurehumanism.co/reports/wa…
A clear explanation of the $wallet 's origins and details is provided here.
