What Is the OP Stack? Modular Framework for L2 Chains

The OP Stack is an open-source, modular set of software components maintained by Optimism that developers use to launch their own optimistic rollup chain. Rather than building a layer-2 blockchain's execution engine, bridge contracts, and sequencer from scratch, teams can assemble a working chain from pre-built, audited pieces.

Why a "stack" instead of one product

Early rollups were built as monolithic codebases: one team, one chain, one set of tightly coupled contracts. That approach worked but made it hard for anyone else to launch a similar chain without duplicating years of engineering and security review.

The OP Stack breaks this down into swappable layers, echoing the broader idea of a modular blockchain:

• Execution layer: Handles transaction processing, typically an Ethereum-equivalent EVM implementation (op-geth).
• Sequencing layer: Orders transactions before they're batched and posted to the settlement layer.
• Settlement layer: Where fault proofs and finalization happen — this is where a chain "checks in" with its parent chain, usually Ethereum.
• Data availability layer: Where transaction data is published so anyone can reconstruct and verify chain state; by default this is Ethereum, though some deployments use alternatives.
• Governance layer: Contracts controlling upgrades, which can be configured differently per chain.

Because each layer is modular, a team can, for example, keep Optimism's execution and sequencing design but choose a different data availability layer for cost reasons, without rewriting the entire chain.

Chains actually running on the OP Stack

Base (Coinbase's L2), Zora, Worldchain, and Optimism's own mainnet (OP Mainnet) all run on the OP Stack. This shared foundation is also the technical basis for the Superchain — a coordinated network of OP Stack chains agreeing on shared security and bridging standards. Being built on the same stack doesn't automatically make chains interoperable, but it does mean their code has been reviewed and battle-tested across more deployments than a fully custom rollup would be.

What developers get from using it

• Faster time to launch: Configuring an existing, audited codebase is faster than writing a rollup's fraud-proof and bridge logic from zero.
• Shared security research: Bugs found and fixed in one OP Stack chain benefit every other chain using the same version of the stack.
• Standardized tooling: Block explorers, indexers, and wallet integrations that support one OP Stack chain often support others with minimal extra work.

What it doesn't automatically give you

Using the OP Stack doesn't mean your chain inherits Ethereum-level decentralization by default. Most OP Stack chains today run a single, centralized sequencer operated by the launching team, and upgrade keys are frequently held by a small multisig rather than a broad decentralized governance process — a pattern sometimes softened by a "security council" that can intervene in emergencies but which itself concentrates power. Anyone evaluating a specific OP Stack chain should look at that chain's own sequencer and governance setup rather than assuming uniform decentralization across the ecosystem.

OP Stack vs. building a fully custom rollup

Factor	OP Stack	Fully custom rollup
Development time	Weeks to months	Months to years
Audit burden	Shared, reused across chains	Entirely new, chain-specific
Flexibility	Configurable within stack's modules	Unlimited, but all custom-built
Ecosystem tooling	Broad compatibility with existing OP Stack tools	Must build or adapt tooling

How upgrades and versioning work across the stack

One underappreciated aspect of the OP Stack is how upgrades propagate. Because many chains share the same underlying codebase, a new version of the stack — say, one that improves fault proof performance or adds a new precompile — can be adopted by multiple chains over time, rather than each chain's engineering team needing to independently discover and implement the same improvement. In practice, chains don't all upgrade in lockstep; each chain's own governance decides when and whether to adopt a given version, which means at any point in time, different OP Stack chains may be running somewhat different versions with different feature sets and security properties.

This has a practical implication for users: two chains both described as "OP Stack chains" aren't necessarily running identical code. If you're evaluating a specific chain's security, it's worth checking which version of the stack it's running and whether it has adopted the latest fault proof and decentralization improvements, rather than assuming uniformity across every deployment.

The role of the Optimism Collective

Governance over the core OP Stack and the broader Superchain concept is handled by the Optimism Collective, a two-house structure combining token holder voting with a separate "citizens' house" intended to represent broader public goods interests rather than purely financial ones. This governance body decides on protocol upgrades, funding allocations, and the standards that define Superchain membership. It's a genuinely novel governance experiment, and like any governance system, its effectiveness depends on ongoing participation and scrutiny from the community it represents, rather than being a solved problem simply by virtue of existing.

Bottom line

The OP Stack turns launching a layer-2 blockchain into an engineering project measured in weeks rather than years, by providing modular, reusable, audited components for execution, sequencing, settlement, and governance. It underpins major chains like Base and forms the technical backbone of the Superchain vision. But using the OP Stack is not a shortcut to decentralization — check each individual chain's sequencer setup and upgrade governance before assuming it behaves like Ethereum itself.