Optimism votes on OPCM and fault-proof incident-response changes

What happened

Optimism opened governance voting on Upgrade Proposal 13, covering OP Contracts Manager, fault-proof incident-response changes, and a DeputyPauseModule.

What changed

The proposal created a concrete path to alter L1 upgrade orchestration, withdrawal-proof validation, dispute-game recovery, and how a designated Pause Deputy could trigger the Superchain-wide withdrawal pause.

What did not change

The March vote did not itself deploy the contracts. It did not shorten the seven-day withdrawal challenge period or require node-operator action.

Confirmed

• The proposal would introduce per-release OP Contracts Manager instances for batched contract deployment and upgrades.
• The proposed OptimismPortal changes separated respected-game selection from retirement timing and changed withdrawal-proof validity checks.
• If deployed, the upgrade would invalidate pending L1 withdrawal proofs once, requiring affected users to re-prove rather than lose assets.
• The DeputyPauseModule would authorize a dedicated key only to invoke the Superchain-wide pause through the existing control path.
• Token House voting was scheduled for March 13–19 with a Citizens' House veto period through March 26.

Still open

• Final approval after the veto period was not established by the candidate's discovery evidence.
• Deployment, final payload verification, and the planned April activation remained outside the March event posture.
• Operational criteria and disclosure practices for Pause Deputy key use required continued review.

What it means for an advisor

• Review the Optimism bridge memo for changed withdrawal-proof behavior and incident-response authority before deployment.
• Plan for possible re-proving of pending withdrawals during the eventual upgrade window.
• Do not treat audits or governance approval as proof that the new controls are risk-free.