A pseudonymous trader says a small group turned a public GitHub code change from crypto custody firm BitGo into a $6 million profit, buying two Robinhood Chain memecoins days before Robinhood listed them and selling into the price spike once each listing went live. The Block checked parts of the trail against onchain records and found wallet activity consistent with the trader’s account, though it could not confirm the profit figures themselves.

The trader, who posts on X as @3i, laid out the approach in a post published Saturday that has since passed 300,000 views. The pitch is simple enough to unsettle anyone who assumes crypto insiders need a hack or a leak to get ahead. Watch two public data sources closely enough, and a major exchange listing becomes visible days before the exchange says a word about it.
A code change meant for engineers, read by traders
Robinhood launched Robinhood Chain, a layer-2 network built on Arbitrum’s tech stack, on July 1. BitGo announced wallet and custody support for the new chain the same day, and Robinhood has separately named algorithmic trading firm Wintermute as one of its largest crypto market makers in an SEC filing. According to @3i, the pair had noticed a pattern in earlier memecoin listings: Wintermute tended to move tokens onto Robinhood Chain about an hour before a listing was announced. That pattern sent them looking for whatever Wintermute itself was reacting to, which led them to BitGo’s public code repository on GitHub.
On July 27, a BitGo developer opened a pull request, a proposed code change anyone can read, on the company’s BitGoJS repository. Buried in the change was a line adding support for “hoodeth:cashcat (Cash Cat) token… on the Robinhood Chain.” It was merged the next day. BitGo then shipped a new release on July 29 that bundled the Cash Cat change alongside support for 99 separate Robinhood Chain stock tokens. To @3i, seeing a memecoin sitting next to a batch of tokenized stocks was the tell. “Why else would cashcat be in there next to their native stock tokens?” they wrote.
Cash Cat had actually launched back on July 1. Robinhood didn’t announce it as a listed, tradeable asset until August 6, more than a week after the pull request and five weeks after the token existed at all. That gap is where the trade lived.
Wintermute’s wallet gave the final signal
After spotting the pull request, the pair started quietly buying Cash Cat, building up to roughly 1.5% of the token’s total supply. But @3i says they were holding off on a bigger position until they got stronger confirmation: Wintermute whitelisting the token or moving it toward Robinhood.
That came, by the trader’s account, on August 3 at 1:48 p.m. ET, when their monitoring bot caught Wintermute approving a trading pool for Cash Cat. “That was the alert we’d been waiting for,” @3i wrote. “The desk had selected a venue to trade the exact coin we were holding.” Onchain records reviewed by The Block show a wallet making its first Cash Cat purchase six minutes later, then buying roughly 12 million tokens in two swaps at 2:20 p.m. ET, a minute after a separate wallet the pair suspected belonged to a Robinhood insider placed an $11,000 limit order. By the end of the day, the wallet had accumulated about 15 million tokens, close to 4% of Cash Cat’s supply. Onchain analytics firm Bubblemaps flagged the same wallet cluster the next morning as part of $2.7 million in purchases spread across a group of fresh wallets.

Robinhood announced Cash Cat was live for trading on August 6. @3i says the pair slept through the token’s initial price spike and still walked away with more than $4 million between them once they sold.
A repeat trade, and a possible trap
The trader says the pair ran the same playbook on PONS, the token behind a memecoin launchpad also built on Robinhood Chain, starting purchases on August 28 and clearing roughly $2 million with friends. But a signal that looked like a September 2 listing turned out, in @3i’s telling, to be closer to a trap set to catch insiders rather than a genuine listing. The trader says the broader edge they describe has since faded.
The claims land against a backdrop that makes them easy to believe. On September 15, the Department of Justice charged two former Robinhood engineers with commodities and wire fraud, accusing them of trading perpetual futures on Hyperliquid ahead of Robinhood listing announcements. Robinhood said at the time that it had investigated the matter itself and reported it to law enforcement. A separate pseudonymous trader, posting as clickless, published their own account the day Cash Cat went live, describing a wallet they believed belonged to a Robinhood insider that placed an early limit order and ultimately lost money.
This isn’t the first time a crypto infrastructure provider’s own public tooling has doubled as an information leak. Wallet provider Web3Auth and the Keplr wallet had to patch a serious vulnerability earlier this year after researchers found a flaw that put user funds at risk (see our coverage of that incident), and the Across Protocol had to respond after attackers hijacked its domain to phish users through channels the public assumed were safe (details here). BitGo’s case is different in kind. Nothing was hacked or stolen. A public, routine pull request simply told anyone paying attention what was coming, in a system where transparency and insider advantage turned out to be the same thing viewed from two angles.
The Block says it confirmed several of the public records @3i cites and found wallet activity consistent with the timeline described, but it could not independently verify who controls the wallets or the exact profit figures claimed. The Block has reached out to Robinhood, Wintermute, BitGo, and @3i for comment.
For anyone who buys into a memecoin the day it lands on a major exchange, this is the part of the trade they never see. By the time Cash Cat and PONS were available to the public, informed buyers had already been accumulating for days or weeks, using nothing more exotic than a GitHub notifications feed and a blockchain explorer. There’s no law against reading public code or public blockchains, which is exactly why stories like this keep recurring. The information asymmetry here isn’t illegal, it’s just unevenly distributed, and for now it rewards whoever is paying the closest attention to infrastructure nobody else thinks to watch.
The bottom line
Open-source code and public blockchains are supposed to be transparent by design. This story is what happens when that transparency becomes an edge only the people watching closely enough get to use. BitGo didn’t break from its own normal practices by merging a routine pull request, and Robinhood hasn’t been accused of wrongdoing here the way its former engineers were in September. But a company moving fast enough to ship code for a listing before it announces that listing is, functionally, broadcasting its own roadmap. For traders who already know to watch GitHub commits and market maker wallets instead of press releases, that roadmap arrives weeks early, and everyone else finds out when the price has already moved.


