Welcome to the next crypto level
← Nexorena

security

Scroll replaces a proof verifier after a security report

The network registered a corrected verifier for version 10 batches on November 10. Scroll said in its report the next day that it found no exploitation in the 748 finalizations it examined.

Nexorena Editorial Team

Scroll replaces a proof verifier after a security report

A verifier already running on Ethereum

Scroll registered a new verifier for version 10 batches on November 10, 2026. The emergency upgrade followed a report received November 3 through its bug bounty program. In a report published November 11, the team said the affected verifier was already deployed on Ethereum mainnet. It was used to check proofs covering multiple batches of Scroll transactions.

The verifier is involved when the layer-2 network submits a proof to Ethereum to establish a new ledger state. The associated public data links finalization to the network state and the reference used for withdrawals. If a proof were validated with public data other than the data it covered, Ethereum could accept a finalization that did not match the proven batch. The fix is intended to restore that link.

A call influenced by the data it received

According to the report, the old contract assembled the data it sent to the OpenVM 2.0 verification layer. Part of the information supplied with a proof could then influence which function the receiving contract ran. In certain conditions, a proof valid for an earlier state could have been accepted with different public data. Scroll said earlier versions of this verifier were unaffected by this combination.

The team said exploitation would have required the permissioned prover role or activation of the forced submission mode. That mode opens only after seven days without finalization and did not activate during the period examined. Scroll said it checked all 748 finalizations completed while the vulnerable verifier was in use. According to the report, all used regular proofs and showed no sign of the manipulation described. Its conclusion that the flaw was not exploited covers the period it checked.

The fix checked against 233 past finalizations

The new contract calls an explicitly defined function in the verifier interface. The contract itself selects the verification values and the hash of the public data it sends. The fix notes say the data passed to the engine that validates a valid proof remains identical. The goal is to retain compatibility while preventing fields received with the proof from changing how the proof is handled.

Scroll said it replayed 233 past finalization transactions on copies of mainnet state. They produced the same state references, while altered copies were rejected. The team also said it simulated the upgrade transactions before signing and compared the deployed code with the public fix. The report thus distinguishes compatibility testing for the new contract from the review of finalizations carried out before it was replaced.

Article sources

Written with love byEthan BrooksMeet this editorial pen name ↗

Explorer Nexorena