Optimism: The OP Stack and Fault Proofs

Source and scope: No single Optimism whitepaper matching the conflicting 2019 and 2021 authorship claims on the earlier pages was verified. This article instead summarizes the official OP Stack specifications and Optimism documentation. It focuses on the OP Mainnet design and fault-proof model documented by those sources; OP Stack chains can configure and upgrade components differently.

Protocol documentation Documentation
Directories Ethereum Whitepapers & Research

OP Mainnet and the OP Stack

OP Mainnet is an Ethereum Layer 2 built on the open-source OP Stack. The OP Stack is modular software used to operate Ethereum Layer 2 chains. It defines components for deriving and executing L2 state from Ethereum data, while allowing deployments to choose supported configurations. A chain’s use of the OP Stack alone does not mean that it shares OP Mainnet’s operators, governance, security settings or upgrade schedule.

In the rollup flow, transactions are ordered on L2 and the chain’s state is derived using data anchored to Ethereum. The protocol specifications describe how a node derives the L2 chain from L1 inputs and how a claim about an L2 state transition can be checked. Details such as sequencing, data publication and deployment configuration must be checked for the specific chain.

Execution and EVM Compatibility

OP Mainnet is designed to run Ethereum-compatible applications and tooling. Compatibility reduces changes needed when deploying many Solidity applications, but it does not mean every network setting, fee, precompile, upgrade or operational assumption is identical to Ethereum L1. Developers and users should consult the active network’s specifications and configuration.

Fault Proofs and Withdrawals

The OP Stack fault-proof system lets participants dispute claims about L2 state. A dispute game narrows disagreement over a proposed execution result until the protocol can resolve a base-case step using a fault-proof virtual machine. The specifications separate the fault-proof program, virtual machine and interactive dispute game, so implementations can use different compatible components.

Optimism announced that governance-approved, permissionless fault proofs went live on OP Mainnet on June 10, 2024. The launch announcement also states that the Optimism Security Council retained authority to intervene and return the system to a permissioned state if the system failed. Fault proofs therefore reduce reliance on a single proposer, but the cited launch design did not remove every governance or emergency intervention power.

Older descriptions that rely on the L2OutputOracle and a simple fixed challenge flow do not describe the current fault-proof path. Consult the current fault-proof and dispute-game specifications for the exact contracts, roles and upgrade state.

Governance, Upgrades and Limits

The OP Stack is open-source, while OP Mainnet and other OP chains have deployment-specific operators and governance arrangements. Protocol upgrades can change the software and security assumptions. The Optimism Collective and Security Council have distinct roles described in official documentation; decentralization is a process with explicit authorities and safeguards, not a binary property established by the label “optimistic rollup.”

  • Fault proofs depend on correct implementations, available data and participants able to monitor and challenge claims within the applicable rules.
  • Ethereum settlement does not eliminate L2 sequencer, bridge, software, governance or upgrade risks.
  • OP Stack chains can differ in their configuration and security assumptions; verify each chain separately.
  • Historical withdrawal and challenge descriptions can become stale as protocol versions change.

Related Terms

See Also

Sources