Robinhood Chain kept producing blocks through a roughly 40-minute app disruption

Robinhood Chain, an Ethereum layer-2 community, kept producing blocks all through its Sept. 4 disruption. A brand new full-day measurement corrects CryptoSlate’s earlier report that block manufacturing stopped for not less than 14 minutes. Separate public-data evaluation discovered that profitable transactions through busy apps fell sharply for about 40 minutes, leaving customers with a actual disruption regardless of the persevering with blocks.

Glass Hull’s Sept. 29 measurement counted 854,255 blocks throughout all 1,440 minutes of Sept. 4 UTC. The longest hole between consecutive recorded block timestamps was two seconds. In the minute starting 12:57 UTC, the reported begin of the supposed halt, the chain produced 592 blocks.

CryptoSlate’s Sept. 5 article stated block manufacturing had halted for not less than 14 minutes. That declare was flawed. Glass Hull measured a totally different 14-minute whole: two separate pauses in posting Robinhood Chain transaction information to Ethereum, from 12:29:47 to 12:38:23 UTC and from 12:42:47 to 12:48:11 UTC. Both ended earlier than 12:57, and neither interrupted the chain’s block manufacturing. L2BEAT’s liveness record lists comparable gaps in Ethereum information submissions. A layer-2 chain can preserve making blocks whereas its separate posting course of is delayed.

How apps have been affected

Walnut’s Sept. 23 analysis discovered profitable site visitors through busy Robinhood Chain apps fell sharply from about 12:37 to 13:20 UTC. Its median busy app accomplished about one fifth of its common profitable transactions in the course of the droop. Walnut reads delayed oracle updates and smart-wallet transaction failures as indicators that tried submissions have been misplaced earlier than reaching blocks. Public chain information go away the purpose of failure unresolved.

QuickNode started investigating elevated Robinhood Chain mainnet latency at 13:10 UTC. At 16:20 UTC, the supplier warned that customers would possibly encounter degraded efficiency and transactions failing to land whereas it investigated sequencer-feed connection points. QuickNode’s file covers its personal service, whereas Walnut’s roughly 40-minute determine measures profitable app site visitors.

In a Sept. 4 statement, @arbitrum stated the chain had no downtime and direct person transactions had no delays. It additionally reported a temporary efficiency influence for some suppliers that depend on the chain’s information stream amid many feed subscribers. The assertion separates direct submissions from supplier providers; Walnut’s app-traffic measurement and QuickNode’s incident present why the excellence issues to customers.

Walnut argues that a low batch-poster tip was outbid throughout an Ethereum payment spike, delaying information posts. Glass Hull leaves the posting gaps’ trigger unresolved. The public file establishes steady block manufacturing alongside impaired app site visitors, whereas the exact off-chain failure level, whether or not in a sequencer queue or an RPC layer, and its connection to the posting delays stay open.

The submit Robinhood Chain kept producing blocks through a roughly 40-minute app disruption appeared first on CryptoSlate.