On-chain investigationFOMO appRobinhood ChainMEV

Front-run 3,532 times: memecoin buyers on Robinhood Chain, nearly all on FOMO

For two weeks in September, someone knew which memecoin a FOMO app user was about to buy on Robinhood Chain, a fraction of a second before the purchase landed. We traced every one of those orders on the blockchain.

At a glance
Between September 12 and 25, three groups of bots bought memecoins on Robinhood Chain a split second before FOMO app users did, then sold into the price rise the users' orders caused. They got ahead of 3,532 orders worth $6.5 million, from 2,319 wallets, nearly all placed through FOMO. Measured against the quotes the users were given, those users lost about $181,000. The bots grossed about $62,000, and a launchpad's fee contract took about $42,000 from their trades. The bots nearly always bought in the split second between Relay, the bridge that fills FOMO's orders, logging an order and filling it. Two of the groups stopped within 86 seconds of each other on September 25. 40,813 USDG is still in their wallets.
3,532
Orders bought ahead of, Sept. 12 to 25, nearly all from FOMO
$181K
Estimated user losses against Relay's own quotes
$62K
Gross profit of the three bot groups
40,813
USDG still in the bots' wallets
Key findingsEach line has its own share link
  1. 3,532

    Memecoin orders a bot bought ahead of between Sept. 12 and 25, worth $6.5 million, from 2,319 wallets. Nearly all came from FOMO.

  2. $181K

    What those users lost against the quotes Relay gave them. The bots grossed about $62,000.

  3. 0.15 s

    How long after Relay logged an order the fastest group bought. All three nearly always bought after the log and before the fill.

  4. 86 s

    Between the last trades of two groups on Sept. 25. Nobody took their place through the next morning.

  5. $42K

    Taken by Pons launchpad's fee contract from the bots' own buys and sells.

  6. 40,813 USDG

    Still in the bots' wallets. One group was funded by a Binance withdrawal.

01 · The orderA $900 buy with a bot in front of it

Just after noon UTC on September 24, a FOMO app user put $900 of USDC into a memecoin called JOLLY. Somebody got there first.

FOMO is a phone app for trading memecoins, built around seeing what your friends buy. Its users keep their money as USDC on Solana, so when one of them buys a coin on Robinhood Chain, the app has to route the order through Relay, a cross-chain bridge. Relay takes the USDC on Solana, and a moment later its solver fills the order: it buys the coin on Robinhood Chain with Relay's own money and sends it to the user.

This time a bot bought JOLLY two blocks before that fill landed, about a fifth of a second earlier. It spent 800 USDG, a dollar stablecoin used on Robinhood Chain. Relay's solver then paid the higher price the bot had left behind, and the user got 6.2% fewer JOLLY than Relay had quoted, about $51 worth. Two blocks later the bot sold into the pump.

That is a sandwich attack: buy just ahead of someone's order, let their buy push the price up, sell straight after. It is a common kind of MEV, the money bots make from the order in which trades land. The on-chain analyst Amir Ormu posted this bot's wallet on X and put its first day at 328 sandwiches.

Bitquery indexes every transaction on Robinhood Chain, so we checked every memecoin order Relay has filled there since late June. The bot on X turned out to be the last of three groups doing the same thing, and the other two had started 10 and 12 days earlier. Between them they got ahead of 3,532 orders, nearly all from FOMO. We measured what those users lost and who ended up with the money, and followed the timing back to where the orders most likely leaked.

02 · The routeHow a FOMO buy reaches Robinhood Chain

Robinhood Chain is Robinhood's own layer-2 on Ethereum, built with Arbitrum, and it has a busy memecoin scene of its own. A single sequencer orders transactions as they arrive, and there is no public mempool, the waiting room where bots on Ethereum watch trades before they land. And paying a higher fee does not buy a better spot.

So a bot cannot spot a normal pending trade and jump it. To get in front, it has to know about the trade before the trade exists on-chain.

A FOMO buy opens that window, because the order starts on another chain. The user deposits USDC with Relay on Solana. Relay logs the order. About 0.4 seconds later, Relay's fill lands on Robinhood Chain.

One order, second by secondRobinhood Chain · Solana
One FOMO buy, second by secondMedian times, counted from the moment Relay logs the order-0.8 s-0.4 s0 s+0.4 s+0.8 sUser deposits USDCRelay logsBots buy the coinRelay's fillTwo groups sellon Solana, about 1 sbefore the fillthe order+0.15 to +0.30 slands, +0.40 s1 to 3 blocks laterShaded: when the three groups bought. Source: Bitquery Robinhood Chain archive; Relay public request records.
The bots bought in the gap between Relay logging an order and filling it.

Every order also carries a slippage limit: the fewest coins the user will take before the trade fails. A bot that pushes the price up can take anything up to that limit, and many FOMO orders went out with limits of 35% to 45%. An order that can be seen early, with that much room in it, is an easy sandwich.

03 · The botsThree groups, 14 days, 3,532 orders

The wallet posted on X belonged to the last of the three groups, which we call the crew. It ran for the final 30 hours of the two weeks, added two wallets on its second morning and moved to four fresh ones for its last hour and a half.

We call the other two the early bot and the holder. The early bot started first and hit the most orders, and the holder, the patient one of the three, went after the biggest ones.

Orders hit per daySept. 12 to 25, 2026
Orders a bot got ahead of, per day, by group01002003004005006001213141516171819202122232425September 2026 (UTC days)Source: Bitquery Robinhood Chain archive. 63 orders fall inside two groups' trades and are counted for both.The early botThe holderThe crew
The crew named on X ran only on the last two days.
GroupActiveOrders hitValue of ordersStake per tradeGross profit
The crew 0x68a0…74d9Sept. 24 to 25738$1,200,991$997$32,760
The early bot 0x2da9…a463Sept. 12 to 252,081$2,867,866$252$22,560
The holder 0x1c60…e398Sept. 14 to 24776$2,605,173$200$6,406
All threeSept. 12 to 253,532$6,525,000$61,725

The crew and the early bot sold within two or three blocks of the user's buy, the classic sandwich. The holder bought ahead the same way, then waited about 24 seconds before selling into the pump.

04 · The fingerprintWhat front-running looks like on a ledger

We found the other two groups by the way they trade. For every order Relay filled since June, we asked who had bought the same coin in the few blocks just before it. A trader who simply likes the same coins shows up at random. A front-runner shows up right before, again and again.

The front-running fingerprintSame coin, blocks around each fill
Buys and sells of the same coin in each block around a FOMO fill (block 0)The crewThe early botThe holdermax 403max 1,334max 479-8-40+4+8-8-40+4+8-8-40+4+8Bot buys of the coin (up)Bot sells of the coin (down)Blocks from the fill · Source: Bitquery, Sept. 12 to 25
Each group buys the coin just before FOMO fills far more often than a few blocks further out.

Two blocks before a FOMO fill, the crew was buying that coin 16 times as often as it did a few blocks earlier, and its sells piled up in the blocks right after. The early bot has the same shape at a bigger scale. The holder buys early and sells later, which is how it got its name.

Busy routers and arbitrage bots trading the same coins show little or no such pile-up. They trade after a fill, once everyone can see it. The same search on Base, where FOMO also sends orders through Relay, found nothing like it.

05 · The costWhat users lost

Relay's public records show what each user was quoted, and the orders the bots left alone got almost exactly that. The crew's victims got a median 8.5% less. That gap is what the front-running cost them.

GroupOrders checkedGot less than quoted (median)Estimated user losses95% range
The crew 0x68a0…74d9689 of 7388.5%$64,454$59,346 to $70,283
The early bot 0x2da9…a463202 of 2,0813.9%$62,749$35,439 to $89,460
The holder 0x1c60…e398207 of 7761.6%$53,814$28,829 to $84,934
All three$181,017$123,615 to $244,677

The crew's figure covers nearly all of its orders, while for the other two we checked random samples, which is why their ranges are wider. Together the three come to about $181,000, roughly three times what the bots grossed. Somebody else was taking a cut.

06 · The splitWhere the money went

About a third of the difference between what users lost and what the bots grossed went to a launchpad. Most of the pools the bots traded were set up by Pons, a Robinhood Chain launchpad. Pons pools take a fee on every swap through a Uniswap v4 hook, 4% on the JOLLY trade. The fee is split between a fee escrow, a buyback vault and Pons's own wallet. Every sandwich adds two swaps, so the hook collected about $42,000 from the bots' trades. On JOLLY the hook's cut was bigger than the bot's gain, and the bot ended that trade about $10 down.

Where the users' money wentEstimated, all three groups
Where the users' estimated losses went$73,584$42,072$65,361Bots, on trades around FOMO ordersPons launchpad's fee hookOther pool fees, other traders, estimate errorTotal $181,017 (range $123,615 to $244,677). The bots lost part of their gain on other trades, ending at $61,725.
The launchpad fee hook took a cut of most bot trades.

The bots made more on their FOMO trades than they kept, because some of their other trades lost money. The rest of the users' loss went to fees in the other pools each order passed through and to other traders, give or take the margin in our estimate. The Pons arbitrage study shows how much of the chain's trading runs through these pools.

07 · The targetsBig orders, loose limits

They went for size. Relay filled 3.3 million memecoin orders on the chain in those two weeks, most of them tiny. The bots got ahead of about one in 40 orders of $2,000 to $5,000, and almost none of the small ones. The small orders they did touch mostly got caught in a sandwich built around a bigger one.

Bigger orders were hit more oftenSept. 12 to 25, 2026
Share of Relay memecoin orders on Robinhood Chain a bot got ahead of, by order sizeUnder $100$100 to $500$500 to $1,000$1,000 to $2,000$2,000 to $5,000$5,000 and up0.03%0.07%0.65%1.47%2.52%1.67%717 of 2,559,047365 of 521,401718 of 111,258677 of 45,932886 of 35,166169 of 10,124Order size = USDG Relay's solver put into the fill. Sept. 12 to 25, 2026. Source: Bitquery Robinhood Chain archive.
About one in 40 orders between $2,000 and $5,000 had a bot in front of it.

They also went for loose limits. Among orders for the same coins that no bot touched, about half had limits above 20%. Among the victims we checked, 85% did. Orders with limits above 20% also lost three to four times as much, on average, as orders capped at 10% or less.

Slippage limitVictim orders checkedGot less than quoted (median)Average loss per order
10% or less210.4%$23
11% to 20%1401.4%$41
21% to 35%3078.0%$97
36% to 45%6307.4%$71

The victims were not a few whales. About 2,300 different wallets were hit, three quarters of them only once, and some were hit by more than one group. Nearly every order we checked came from FOMO. The rest came from other apps that also route through Relay.

Victim wallets on Robinhood ChainCount
Different wallets hit2,319
Hit once1,763
Hit 2 to 4 times470
Hit 5 to 9 times76
Hit 10 times or more10
Hit by more than one group322
Most-hit wallet0x6fea…0a0a: 26 times, $97,392 of orders
Orders checked that came from FOMOcrew 99%, early bot 96%, holder 99%

08 · The leakWhere the tip came from

To front-run a FOMO buy, a bot has to know which coin is coming before Relay's fill lands. The chain does not tell it. The Solana deposit carries only an amount and an order number, and the buyer's wallet on Robinhood Chain almost never does anything first. The tip came from somewhere off-chain.

Timing shows roughly where. Robinhood Chain makes about 10 blocks a second, which lets us place each trade, the bots' buys and Relay's fills alike, to within about a tenth of a second. Relay logs each order about 0.4 seconds before its fill. All three groups bought after that log entry existed, in nearly every order we timed.

GroupBot buys, after Relay logs the order (median)Bot bought before the log existedRelay's fill, after the bot buys (median)Orders timed
The crew 0x68a0…74d90.15 s3.8%0.20 s689
The early bot 0x2da9…a4630.24 s2.0%0.11 s202
The holder 0x1c60…e3980.30 s3.4%0.10 s207

Someone at FOMO would have known sooner, when the user asked for a quote, and could have bought earlier. The three groups almost never did: fewer than 4% of their buys came before Relay's log. So the leak most likely sits in that last 0.4 seconds, somewhere between Relay logging the order and the fill landing. Whoever read it there saw the coin, and since the bots favored loose limits, most likely the limit too.

That could be Relay's own systems, data Relay published, or the path its fill takes to the chain. We cannot tell which. Relay's public order feed today shows pending FOMO orders with no coin and no minimum. We watched it for two minutes, and every FOMO order we caught mid-flight was blank. What it showed before the bots stopped, we cannot see. Relay's logs can settle it: who read these order numbers during those two weeks, and what changed on the afternoon the bots went quiet.

09 · The money trailThree groups, three funding trails

The three groups share a method and even some victims, but as far as we can follow the money, two hops back, they do not share funding.

GroupWhere the money came fromHow it reached Robinhood Chain
The crew0.531 ETH from a Binance hot wallet on Ethereum, Sept. 24 08:47 UTCBridged to Robinhood Chain through Relay 24 s later
The early bot5,499 USDC on Base from an exchange hot wallet, Sept. 10Bridged through Relay on Sept. 12 and 13
The holderBNB on BSC, Aug. 22Bridged through LI.FI and Relay

The crew's hub wallet, the one that paid its bots, was brand new on Ethereum. Its first ETH came from a wallet that our address labels mark as a Binance hot wallet, part of Binance's proof of reserves. Within half a minute the hub bridged it to Robinhood Chain through Relay. Binance can tie that withdrawal to an account.

The early bot's money came from a Base wallet, funded by an exchange hot wallet that paid USDC to more than 100,000 addresses in September. The holder's funder bridged BNB in from BSC through LI.FI, another bridge service, in August. Each trail can be followed with the Bitquery MCP.

10 · The stopIt stopped, and the money is still there

The early bot sent its last transaction on the afternoon of September 25. The crew sent its last 86 seconds later. The holder had already stopped the day before. Through the early hours of September 26, no contract on Robinhood Chain took their place. The closest match made 10 early buys, where chance alone gives about 1, and no burst of sells after them.

GroupLast transaction (UTC)
The holder 0x1c60…e398Sept. 24, 12:01:33
The early bot 0x2da9…a463Sept. 25, 14:43:25
The crew 0x68a0…74d9Sept. 25, 14:44:51
Closest match since (to Sept. 26, 03:11)10 early buys, where chance gives about 1; no burst of sells

FOMO orders still went out with loose limits after the stop, so whatever ended it was not a change to the app's settings. More likely, something the bots relied on was switched off.

The bots still hold 40,813 USDG, and none of it had moved by the morning of September 26. USDG is issued by Paxos, and its contract lets Paxos freeze an address, which Paxos says it does when it receives a formal legal order. That is the part of the bots' take that can still be held in place.

WalletWhoUSDG held
0xfaba…c6ceThe crew, hub2,100.00
0xb49d…8c44The crew, round 1 wallet4,156.84
0xd759…cd65The crew, round 1 wallet4,423.55
0xf9ef…3a74The crew, profit wallet15,864.54
0x14cf…e9a2The crew, round 2 wallet1,466.50
0x0e56…508fThe crew, round 2 wallet1,510.30
0x5d10…4b67The crew, round 2 wallet715.11
0xebca…8ac7The crew, round 2 wallet2,049.99
0x2da9…a463The early bot, contract6,772.85 + 8.42 ETH
0x8eee…ba16The holder, wallet1,753.51
Total40,813.19

Traders do not have to wait for any of that. A tighter slippage limit caps what any bot can take, because an order that would lose more than its limit fails and gets refunded instead.

Slippage capVictim orders that would have been refundedShare of the loss it would have blocked, at least
20%6%4%
10%33%17%
5%58%44%

So who knew what FOMO users were about to buy? Someone who could read each order, its coin and most likely its limit, in the split second after Relay logged it. Three groups acted on that for two weeks and cost people buying memecoins on their phones about $181,000. Then two of them went quiet within a minute and a half of each other. The evidence that could name the source sits in Relay's logs.

Method: we checked every memecoin order Relay filled on Robinhood Chain from late June to September 25, using Bitquery's Robinhood Chain data. An order counts as front-run when a bot bought the same coin up to five blocks before it and still held that coin when the order filled. Each user's loss is how far their fill fell short of Relay's quote. Bot profits are the dollars and ETH each group ended up with. Holdings are as of the morning of September 26. Address labels are Bitquery's own.

WhatAddress or transaction
Crew bot contract0x68a0…74d9
Crew first wallet0x44c0…74dd
Early bot contract0x2da9…a463
Holder contract0x1c60…e398
Relay's settlement contract0xccc8…15be
Pons fee hook0xe5e7…e044
JOLLY: bot buys0xc13a7e…34d3
JOLLY: Relay's fill0x6c122e…ec6f
JOLLY: bot sells0xda3b41…173f
Follow it yourself

The wallets are public

Every bot wallet, contract and funding trail named here is on a public chain. You can pull the trades, follow the USDG and check whether anything moves after we published.

Robinhood Chain tradesTransfer tracingAddress labelsCross-chain flows
Open the Bitquery MCP →Holdings as of September 26, 2026, 06:12 UTC
Scope, limits and attribution

This article is provided for informational and educational purposes only and reflects analysis of publicly available on-chain data and Relay's public request records as of the times stated. It does not constitute legal, financial, compliance, or investment advice.

Wallets and contracts are identified by address only. Nothing here states who controls them, and describing a wallet's trades is not an accusation against any person. User losses are estimates with the ranges shown.

References to FOMO, Relay, Pons, Paxos, Binance, LI.FI and any other party describe on-chain activity or public statements. This article does not find that any of them leaked orders or took part in the trading described; where the information came from is stated as open.

Nothing herein should be relied upon as a definitive determination of fact. Readers should conduct their own independent verification before taking any action. The authors and publisher accept no liability for any loss or damage arising from the use of this article.

Reported by Gaurav Agarwal for Bitquery Research, with AI tools; every figure was checked against the raw data.

Watch Robinhood Chain trades as they land

Bitquery serves every trade on Robinhood Chain, for any pool or token, as it lands.