Wu Shuo learned that the Ethereum L2 network Starknet released a post-incident analysis report regarding the brief mainnet outage on Monday this week, stating that the accident was caused by state inconsistency between the execution layer (blockifier) and the proving 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 relevant transactions did not receive L1 finality confirmation. This incident triggered a block reorganization, with approximately 18 minutes of on-chain activity being rolled back. This is the second major disruption since 2025, with the previous occurrence in September caused by a sequencer vulnerability that led to over 5 hours of downtime and rolled back approximately 1 hour of on-chain activity.
Ця сторінка може містити контент третіх осіб, який надається виключно в інформаційних цілях (не в якості запевнень/гарантій) і не повинен розглядатися як схвалення його поглядів компанією Gate, а також як фінансова або професійна консультація. Див. Застереження для отримання детальної інформації.
Wu Shuo learned that the Ethereum L2 network Starknet released a post-incident analysis report regarding the brief mainnet outage on Monday this week, stating that the accident was caused by state inconsistency between the execution layer (blockifier) and the proving 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 relevant transactions did not receive L1 finality confirmation. This incident triggered a block reorganization, with approximately 18 minutes of on-chain activity being rolled back. This is the second major disruption since 2025, with the previous occurrence in September caused by a sequencer vulnerability that led to over 5 hours of downtime and rolled back approximately 1 hour of on-chain activity.