Robinhood Chain did not stop producing blocks on Friday. What stopped, for a total of 14 minutes across two separate gaps, was the chain’s batch data reaching Ethereum.
Those batch submissions are what place Robinhood Chain’s data on Ethereum so anyone can reconstruct the chain and verify it. They also allow funds to exit to Ethereum. Robinhood Chain posts more of that data than any other network, which made the delay the largest single interruption the blob market could produce.
Arbitrum said Ethereum’s blob market caused the delay. That explanation fits the second gap, which started after blob prices moved above the ceiling Robinhood Chain’s poster had been bidding. It does not fit the first and longer gap, which lasted 8 minutes and 36 seconds while Ethereum blocks still had 263 unused blob slots and priced them at 0.0086 gwei, against the poster’s standing bid of 0.0616 gwei.
At 2:19 p.m. New York time, Arbitrum wrote: 「Robinhood Chain experienced no downtime. Earlier today, Robinhood Chain experienced batch posting delays due to L1 market blob behavior. Direct user transactions experienced no delays. Some infrastructure providers that rely on Robinhood Chain’s data stream experienced a brief performance impact due to a high number of feed subscribers. Robinhood Chain remains operational.」 Before that post, messages on X and two crypto outlets had reported that the network stopped producing blocks for around 14 minutes. Within an hour, the post had drawn about 24,500 views, 314 likes, and 40 replies.
Robinhood has published no technical account of the incident, and its chain documentation lists no status page.
Blocks never stopped
According to block data read from Robinhood Chain’s Blockscout explorer, the chain produced 106,756 blocks between 12:00 and 15:00 UTC, an average of one every 101 milliseconds. Block 54,248,341 carries a 12:00:00 timestamp and block 54,355,097 carries 15:00:00, a count consistent with uninterrupted production at that rate.
Blocks inside the window flagged by traders still carried activity. Block 54,266,500 at 12:30:37 UTC contained 19 transactions, block 54,270,000 at 12:36:34 carried 14, and block 54,274,000 at 12:43:21 carried 22. Every sampled block between 12:28 and 12:50 UTC held between 14 and 22 transactions.
The missing piece was data posted to Ethereum
The delay sat on Ethereum. Robinhood Chain’s batch poster, the address 0xDaa5…87F4 identified by L2BEAT, submits blob transactions to the chain’s sequencer inbox contract at a median interval of 12 seconds.
It went 8 minutes and 36 seconds without posting from 12:29:47 to 12:38:23 UTC, then stayed silent for another 5 minutes and 24 seconds from 12:42:47 to 12:48:11.
Those two gaps total 840 seconds, exactly 14 minutes, matching the figure that circulated on Friday as the duration of an apparent block-production halt. Across the 18 minutes and 24 seconds between the start of the first gap and the end of the second, the poster landed batches at nine separate moments, against roughly 92 that its median cadence would imply. Software tracking the chain through Ethereum batch data rather than through its blocks would have seen 14 minutes with nothing arriving.
Across the nine hours from 11:00 to 20:00 UTC, 26 intervals ran 60 seconds or longer, and 19 of them fell between 12:10 and 14:51. Those figures come from 2,279 consecutive blob transactions sent by that address, read from Blobscan.
Ethereum still had spare blob capacity during the first gap
A Robinhood Chain batch carries three blobs. Ethereum blocks held 21 at most on Friday, and no block in a sample of 600 exceeded that count. That makes the key test straightforward: while Robinhood Chain’s batches were missing, how many Ethereum blocks still had at least three blob slots free?
During the first gap, 21 of the 29 Ethereum blocks that carried any blobs had at least three free slots, and the window held 263 unused slots in total. The blob base fee averaged 0.0086 gwei and peaked at 0.0152 gwei, against the 0.0616 gwei Robinhood Chain’s poster had bid on its last transaction before the gap began.
| Measured on Ethereum | Gap 1, 8m 36s | Gap 2, 5m 24s |
|---|---|---|
| Blocks with three or more blob slots free | 72% | 81% |
| Unused blob slots in the window | 263 | 223 |
| Blob base fee, mean | 0.0086 gwei | 0.0625 gwei |
| Blob base fee, peak | 0.0152 gwei | 0.0906 gwei |
| Robinhood Chain standing bid | 0.0616 gwei | 0.0616 gwei |
The second gap reads differently. Blob base fee averaged 0.0625 gwei through that stretch, above the standing bid, and the batch that ended the gap raised the ceiling to 0.8187 gwei.
Blob price is not the only factor in inclusion. A blob transaction also competes on execution-layer fee, and block builders sometimes carry fewer blobs than the limit allows to keep blocks moving quickly through the network. Still, neither point accounts for an 8 minute 36 second absence across 263 open slots at about one-twelfth of the price the sender had already offered.
Bids climbed sharply once posting resumed
The poster’s fee ceiling shows what changed once batches started landing again. It bid 0.0616 gwei per unit of blob gas going into the first gap, then 0.2463 gwei on the batch that ended it, four times higher, at a moment when base fee had reached 0.0434.
It bid 0.8187 gwei on the batch that ended the second gap and reached 1.4239 gwei at 12:53:59, roughly 10 times the prevailing base fee.
The public record does not establish whether that escalation reflected the poster responding to a rising market or recovering from a fault of its own. Robinhood has not said which one it was, and mempool data that could show whether its batches were already broadcast and waiting during the first gap is not publicly retained.
The 21-blob ceiling and a later price squeeze
Blob space did tighten on Friday, but later than the first gap. Blob base fee averaged 0.0055 gwei across the 85 minutes to 12:25 UTC, then climbed to 0.1473 gwei by 12:53:23, 27 times the earlier level.
Ethereum blocks carried an average of 6.92 blobs in the calm period and 11.99 between 12:25 and 13:00 UTC. Eight percent of blocks in that window carried 21 blobs, the highest count observed in any block.
At the peak fee, posting a three-blob Robinhood Chain batch cost about $0.14.
Base drove the broader jump in blob demand
The demand that pushed blob prices higher came from Base. Robinhood Chain’s own posting rate stayed nearly unchanged: its batch poster sent 476 blobs in the 35 minutes to 11:35 UTC and 477 in the 35 minutes to 13:00 UTC, according to Blobscan.
Base nearly tripled its usage over the same comparison, rising from 222 blobs to 593. Arbitrum One went from 48 to 135, while total blob supply across all senders rose 59%, from 1,058 to 1,678.
Robinhood Chain still accounted for 28% of every blob posted to Ethereum during the crunch and 45% in the calmer window before it. In both samples, it remained the largest single sender.
Base’s batcher posts six blobs at a time, so it buys more space by posting more often. It submitted a batch every 55 seconds through the morning, then sent 45 batches in the 10 minutes from 12:30 UTC, one every 13 seconds and four times its morning rate, before settling near one every 30 seconds for the rest of the afternoon.
What changed was traffic on Base itself. Blocks read through Base’s public RPC endpoint carried an average of 1,428 transactions in those 10 minutes, versus 174 at 12:20. One block held 2,031 transactions. Another burned 360 million gas against Base’s 400 million gas limit. Base’s own base fee also left the 0.005 gwei floor it had held all morning and reached 0.0193 gwei by 12:40.
About 31% of sampled Base transactions in the 12:40 UTC window went to four unverified contracts that emit no event logs and move no tokens, each burning between 54,000 and 144,000 gas. None carries a public label. One of them has processed 4.43 million transactions since deployment and recorded a single token transfer, according to Base’s Blockscout explorer.
Robinhood and Base did not reply to requests for comment by press time.
Why batch posting matters
Robinhood Chain’s sequencer confirms transactions for users on its own. Posting batches to Ethereum is what places the data where anyone can reconstruct the chain and challenge it, and what allows funds to leave for Ethereum.
Robinhood operates the chain’s only sequencer. L2BEAT also flags a precompile, ArbFilteredTransactionsManager, that lets an authorized filterer register a transaction hash and cause the state transition to fail it, including transactions that were force-included. There is no delay on code upgrades. Users had no alternative route while batches were queued.
Software that reads the chain’s sequencer feed rather than its blocks would have seen the degradation. Chainstack’s open-source decoder uses that path to view transactions before execution, which matches the gap between monitoring tools reporting a halt and block data showing continued production.
Fees, TVL, and trading activity kept rising
Robinhood Chain took in $4.59 million in chain fees over 24 hours, up 3.1%, according to DefiLlama. Total value locked reached $839.7 million, up from $783.1 million a day earlier. DEX volume was $1.69 billion, up 8.6% on the day and 98.2% over seven days.
The chain launched its mainnet on July 1 as infrastructure for tokenized securities, then shifted toward memecoins as launch platforms paired them against stock tokens. It passed Solana on tokenized stock volume in late July, overtook Base on daily active users three weeks after launch, and topped Ethereum on daily application revenue on Aug. 29.
Under Arbitrum’s Expansion Program license, Arbitrum collects 10% of the chain’s fees, split 8% to the DAO treasury and 2% to development funding.
According to CoinGecko data at 19:30 UTC on Sept. 4, ARB traded at $0.1327, down 5.7% over 24 hours, for a market capitalization of $886.2 million. PONS, the launchpad token native to the chain, was at $0.6903, up 12.8%. ETH traded at $2,457.42, down 2.2%.
Data sources and methodology
Robinhood Chain block data in the report came from the chain’s Blockscout explorer. Batch posting, blob capacity, and blob market data came from Blobscan, covering 2,279 blob transactions from the chain’s batch poster and 786 Ethereum blocks between 11:00 and 14:00 UTC on Sept. 4. Free-slot counts assume the 21-blob maximum observed across that window and a separate sample of 600 blocks.
Base transaction, gas, and base fee figures came from 10 blocks sampled per 10-minute bucket through Base’s public RPC endpoint, with destination contracts counted across 2,899 transactions in the 12:40 UTC window. Fee, TVL, and volume figures came from DefiLlama, while prices came from CoinGecko at 19:30 UTC on Sept. 4.