Wu Shuo learned that Ethereum L2 network Starknet released a post-mortem analysis report on this week's brief mainnet downtime, stating that the cause of the incident was state inconsistency between the execution layer (blockifier) and the proof layer: under a specific combination of cross-function calls and rollbacks, the execution layer incorrectly recorded state writes that had been rolled back, causing transaction execution anomalies. The related transactions did not receive L1 finality confirmation. This incident triggered a block reorganization, with approximately 18 minutes of on-chain activity rolled back. This is the second major outage since 2025, with the previous one in September caused by a sequencer vulnerability that resulted in over 5 hours of downtime and rolled back approximately 1 hour of on-chain activity.
Halaman ini mungkin berisi konten pihak ketiga, yang disediakan untuk tujuan informasi saja (bukan pernyataan/jaminan) dan tidak boleh dianggap sebagai dukungan terhadap pandangannya oleh Gate, atau sebagai nasihat keuangan atau profesional. Lihat Penafian untuk detailnya.
Wu Shuo learned that Ethereum L2 network Starknet released a post-mortem analysis report on this week's brief mainnet downtime, stating that the cause of the incident was state inconsistency between the execution layer (blockifier) and the proof layer: under a specific combination of cross-function calls and rollbacks, the execution layer incorrectly recorded state writes that had been rolled back, causing transaction execution anomalies. The related transactions did not receive L1 finality confirmation. This incident triggered a block reorganization, with approximately 18 minutes of on-chain activity rolled back. This is the second major outage since 2025, with the previous one in September caused by a sequencer vulnerability that resulted in over 5 hours of downtime and rolled back approximately 1 hour of on-chain activity.