Robinhood Chain kept producing blocks through a roughly 40-minute app disruption
New full-day measurements correct the block-halt claim, while separate data show a steep drop in successful app traffic. The post Robinhood Chain kept producing blocks through a roughly 40-minute app disruption appeared first on CryptoSlate.
Robinhood Chain, an Ethereum layer-2 network, kept producing blocks throughout its Sept. 4 disruption. A new full-day measurement corrects CryptoSlate's earlier report that block production stopped for at least 14 minutes. Separate public-data analysis found that successful transactions through busy apps fell sharply for about 40 minutes, leaving users with a real disruption despite the continuing blocks.
Glass Hull's Sept. 29 measurement counted 854,255 blocks across all 1,440 minutes of Sept. 4 UTC. The longest gap between consecutive recorded block timestamps was two seconds. In the minute beginning 12:57 UTC, the reported start of the supposed halt, the chain produced 592 blocks.
CryptoSlate's Sept. 5 article said block production had halted for at least 14 minutes. That claim was wrong. Glass Hull measured a different 14-minute total: two separate pauses in posting Robinhood Chain transaction data to Ethereum, from 12:29:47 to 12:38:23 UTC and from 12:42:47 to 12:48:11 UTC. Both ended before 12:57, and neither interrupted the chain's block production. L2BEAT's liveness record lists comparable gaps in Ethereum data submissions. A layer-2 chain can keep making blocks while its separate posting process is delayed.
Related ReadingWalnut's Sept. 23 analysis found successful traffic through busy Robinhood Chain apps fell sharply from about 12:37 to 13:20 UTC. Its median busy app completed about one fifth of its usual successful transactions during the slump. Walnut reads delayed oracle updates and smart-wallet transaction failures as signs that attempted submissions were lost before reaching blocks. Public chain data leave the point of failure unresolved.