#加密社区
The chain never stopped, but data didn’t reach Ethereum for 14 minutes. This happened on the proprietary L2 of a U.S. retail brokerage.
📢 进群聊数据动态
This chain went live on July 1 and runs on Arbitrum’s tech stack.
On September 1, its daily fee revenue hit a record $3.75 million, breaking records for the fourth straight day.
In its first two months, cumulative fees were about $11.48 million, putting it on track for an annualized pace of $60 million.
On September 4, the address sending data to Ethereum experienced two periods of silence.
8 minutes 36 seconds plus 5 minutes 24 seconds, exactly 14 minutes.
The on-chain data batches did not arrive on Ethereum.
During those three hours, it actually produced 106,000 blocks, averaging one every 101 milliseconds.
The official line was that the chain did not stop and user transactions were not delayed.
But third-party infrastructure that depends on on-chain data saw a complete blank.
The cause of the second interruption pointed to the blob market.
Ethereum’s bidding cap was undercut by market price.
Afterward, they raised the bidding cap to 0.8187 and things returned to normal.
There was no loss of funds and no unauthorized access.
This brings the issue back to one definition.
When it comes to L2 availability, whose perspective should count?
Users felt nothing, but third-party infrastructure went dark for 14 minutes.
What do you think about this?
The chain never stopped, but data didn’t reach Ethereum for 14 minutes. This happened on the proprietary L2 of a U.S. retail brokerage.
📢 进群聊数据动态
This chain went live on July 1 and runs on Arbitrum’s tech stack.
On September 1, its daily fee revenue hit a record $3.75 million, breaking records for the fourth straight day.
In its first two months, cumulative fees were about $11.48 million, putting it on track for an annualized pace of $60 million.
On September 4, the address sending data to Ethereum experienced two periods of silence.
8 minutes 36 seconds plus 5 minutes 24 seconds, exactly 14 minutes.
The on-chain data batches did not arrive on Ethereum.
During those three hours, it actually produced 106,000 blocks, averaging one every 101 milliseconds.
The official line was that the chain did not stop and user transactions were not delayed.
But third-party infrastructure that depends on on-chain data saw a complete blank.
The cause of the second interruption pointed to the blob market.
Ethereum’s bidding cap was undercut by market price.
Afterward, they raised the bidding cap to 0.8187 and things returned to normal.
There was no loss of funds and no unauthorized access.
This brings the issue back to one definition.
When it comes to L2 availability, whose perspective should count?
Users felt nothing, but third-party infrastructure went dark for 14 minutes.
What do you think about this?
