
Robinhood Chain kept producing blocks through a roughly 40-minute app disruption
- —The chain produced 854,255 blocks on Sept. 4, with a maximum two-second gap
- —In the minute starting 12:57 UTC, the chain produced 592 blocks
- —Walnut: successful app transactions dropped from 12:37 to 13:20 UTC
- —QuickNode reported rising latency and failed transactions from 13:10 UTC
Why it matters: The case shows an L2 can keep producing blocks while users still lose transactions due to oracle and RPC failures.
Source: CryptoSlate