Batch commitment on hold

Incident Report for Scroll

Postmortem

On Nov 10th, 2024, at 11:52 UTC, the Scroll engineering team deployed a new version of the Scroll rollup-relayer and gas oracle. Due to an incorrect configuration file, outdated batches were committed to L1.

To resolve this, we stopped the rollup-relayer and reverted the affected batches (346815, 346816, 346817, 346818). Afterward, the rollup-relayer resumed normal operation, and Scroll batches are now being committed and finalized as expected as of Nov 10th, 2024, at 15:05 UTC.

Users funds were not at risk, and there was no chain reorg on Scroll.

Posted Nov 17, 2024 - 13:25 UTC

Resolved

This incident has been resolved.

Posted Nov 10, 2024 - 15:05 UTC

Monitoring

A fix has been implemented and we are monitoring the results.

Posted Nov 10, 2024 - 13:12 UTC

Identified

The issue has been identified and a fix is being implemented.

Posted Nov 10, 2024 - 12:32 UTC

Investigating

We are currently investigating this issue.

Posted Nov 10, 2024 - 11:52 UTC

This incident affected: Scroll (Sequencer (rollup node)).