Layer 2 blockchain · settles to Ethereum
OP Mainnet ticker OP
Summary
Optimistic rollup on Ethereum. A sequencer orders transactions into L2 blocks; batch data and state output proposals are posted to Ethereum, and op-node derives and verifies L2 blocks from those Ethereum inputs. Permissionless fault proofs went live on OP Mainnet on 10 June 2024. In August 2024 the Optimism Foundation, acting as Deputy Guardian, switched to a permissioned fallback that limited output proposals to a trusted proposer while audit findings were fixed; the Granite upgrade, scheduled for 11 September 2024, was set to restore permissionless proposing. As of the review date anyone can propose or challenge outputs, with a challenge period of about one week plus an airgap before withdrawals finalize. Block production does not use its own stake or work. 1234151617
Design
- System
- Layer 2 blockchainOP Mainnet (chain ID 10) is an optimistic rollup on Ethereum built with the OP Stack. ETH is the gas asset; OP is a governance token. Other OP Stack and Superchain chains, including Base, are separate networks not described here.
- Settles to
- EthereumBatch data and output proposals are posted to Ethereum. Standard Bridge deposits usually arrive in 1 to 3 minutes; withdrawals to Ethereum complete after about 7 days because of the fault-proof challenge period.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One sequencer (write-only public endpoint mainnet-sequencer.optimism.io); the operating entity is not named in the reviewed docs. Output proposals are permissionless under fault proofs. Users can bypass the sequencer by sending transactions to the OptimismPortal contract on Ethereum; Optimism documents a 12-hour sequencing window for including them if the sequencer is down or censoring.
- Fork choice
- No open L2 fork choice: the canonical chain is derived from data posted to Ethereum, and disputed outputs are settled by onchain fault-proof games. The Security Council holds the Guardian role, which can pause withdrawals, blacklist games or revert to a permissioned system. A Safe module on the Guardian Safe also lets the Optimism Foundation pause withdrawals, and in 2024 the Foundation used a Deputy Guardian role to switch to permissioned output proposals.
Qualifications
- Scarce resource · Not applicable. OP Mainnet block production uses no stake or work of its own; security is derived from Ethereum plus fault proofs and Guardian backstops.
- Finality · Partial. Latest, safe and finalized L2 heads are distinct from Ethereum settlement of a withdrawal, so OP Mainnet's finality does not fit the single-chain finality categories used for base-layer chains.
- Superchain interop · Not applicable. Optimism's Upgrade 20 proposal (9 September 2026) says it positions the dispute system for interop but does not enable it; each chain keeps its own AnchorStateRegistry and DisputeGameFactory contracts. Superchain interop is not active on OP Mainnet as of the review date; registry membership is not live interop.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Decentralized sequencing: a single sequencer orders transactions. Withdrawals to Ethereum take about 7 days. The Guardian can pause withdrawals, and a 2-of-2 upgrade key held by the Optimism Foundation and the Security Council can replace bridge and proof contracts instantly, with no onchain delay and no exit window for users.The security emphasis refers to Ethereum data availability and permissionless fault proofs. L2BEAT rates OP Mainnet Stage 1: proofs are permissionless, but contracts stay instantly upgradable by a 2-of-2 of an Optimism Foundation 5-of-7 multisig and the Security Council multisig, which is part of the trust model.
- Full node at home
- Practical at home 7Optimism lists 16 GB RAM and a reasonably modern CPU; as of June 2025 a full-node snapshot was about 700 GB, growing about 100 GB every six months (archive about 14 TB on NVMe). A node also needs an Ethereum L1 RPC and beacon endpoint, so independent verification means running or trusting an Ethereum node too.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | A protocol-level trust-minimized swap mechanism on OP Mainnet was not reviewed. |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Unknown | A light-client verification path for OP Mainnet was not reviewed. |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to OP Mainnet was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | OP Mainnet runs EVM contracts; Safe lists smart-account deployments on chain ID 10. 110 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Independent softwareLimited scope | Safe lists its Safe Recovery Module on OP Mainnet (chain ID 10) on its supported-networks page (retrieved 2026-09-27). A recovery module that an account sets up in advance lets it regain control without the lost key, which is part (b). Safe publishes it; no first-party implementation was cited. Scope is limited: no feature for reclaiming, cancelling or delaying a payment (part a) was cited. The module was checked only against Safe's network listing, not tested on OP Mainnet. 10 |
| Rollups | Unknown | Rollups anchored to OP Mainnet (L3s) were not reviewed. OP Mainnet itself is a rollup on Ethereum; see the mechanism and Ethereum-dependency sections of this profile. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Established in the ecosystemUniswap v3 | Uniswap documents v3 contract deployments on Optimism (factory 0x1F98431c8aD98523631AE4a59f267346ea31F984). Liquidity depth was not measured and other venues were not reviewed. 11 |
| Issuer-native stablecoins | Established in the ecosystemUSDC (Circle) | Circle lists natively issued USDC on OP Mainnet (0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85). Native means issuer-issued on OP Mainnet, not a protocol asset. 12 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on OP Mainnet were not reviewed. |
| Bridges | Native to the protocolOP Standard Bridge (Ethereum to OP Mainnet) | The Standard Bridge locks or burns on one side and mints or unlocks on the other; deposits usually take 1 to 3 minutes and withdrawals about 7 days. Third-party bridges were not reviewed. Risk: Withdrawals depend on fault proofs; the Security Council Guardian can pause them or revert to a permissioned system, and the Optimism Foundation can pause them through a module on the Guardian Safe. Upgrades need a 2-of-2 of an Optimism Foundation 5-of-7 multisig and the Security Council and take effect with no onchain delay, so users have no exit window before an unwanted upgrade. Regular upgrades pass a 7-day offchain governance veto period; emergency upgrades do not. A token can have several bridged versions, so a wrong address can lose funds. 45616 |
| Block explorers | Established in the ecosystemOptimism Explorer (explorer.optimism.io), OP Mainnet Etherscan (optimistic.etherscan.io) | Optimism documentation lists explorer.optimism.io for OP Mainnet, and OP Mainnet Etherscan was serving current OP Mainnet blocks at review time. Explorer indexes are not canonical consensus. 123 |
| Hardware wallets | Established in the ecosystemTrezor (Safe 3, 5, 7), Ledger (lower confidence) | See the custody section: Trezor Suite includes the OP Mainnet network, and Ledger Wallet code includes it behind a switch that Ledger's templated Optimism page suggests is on, so the Ledger rating is lower confidence. 13141822 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Unknown | Can: Set up an Optimism account in the Ledger Wallet app, per Ledger's Optimism coin pageLower confidence. Ledger Wallet's code includes the OP Mainnet (Optimism) network behind a feature switch that is off by default, and the remote setting that can switch it on for users could not be read. Ledger's Optimism page is a templated coin page: it says an Optimism account can be set up and managed in Ledger Wallet but names neither the network nor a device app, and it is taken as the sign that the switch is on. 1318192021 |
| Trezor | Native supportSame as native: Unknown | Can: Manage Optimism assets with Trezor Safe 3, Safe 5 and Safe 7 in Trezor Suite, per Trezor's Optimism page Can: Use the device through MetaMask or Rabby, which Trezor names as compatible appsTrezor lists Optimism as the supported network, and Trezor Suite's current network code includes OP Mainnet (chain ID 10); coverage of older models and of contract interactions was not reviewed. 1422 |
Public data
Your AI can request these lookups through the connection. The website itself runs no lookups. Networks: mainnet.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Available | native ETH balance, nonce and code presence at provider-reported latest state |
| Tokens and assets | Available | paginated Blockscout-indexed ERC-20 plus aggregate ERC-721/ERC-1155 contract balances |
| NFTs | Available | paginated Blockscout-indexed ERC-721 and ERC-1155 token IDs with exact quantities |
| Transactions | Available | transaction and receipt at one public RPC plus exact provider-relative confirmations |
Sourced developments
Developments: Review overdue Reviewed Sep 26, 2026; next review was due Oct 6, 2026.
Publication date · newest first
-
op-proposer v1.16.6 was published as a recommended operator release
The official release recommends v1.16.6 for op-proposer operators and states that its image was rebuilt on a patched base with no op-proposer code changes. A component release is not evidence of a protocol activation.
- Type:Release
- Proposal:Not applicable
- Release:Released recommended
- Activation:Client release not protocol activation
Sources: OP Labs — op-proposer v1.16.6 (external site) · OP Labs — Optimism monorepo release feed (external site)
-
op-challenger v1.10.0 was published as a recommended operator release
The official release recommends v1.10.0 for op-challenger operators, with a patched base image and ZK-proof groundwork explicitly described as not running in production. A component release is not evidence of a protocol activation.
- Type:Release
- Proposal:Not applicable
- Release:Released recommended
- Activation:Client release not protocol activation
Sources: OP Labs — op-challenger v1.10.0 (external site) · OP Labs — Optimism monorepo release feed (external site)
-
Upgrade 20 proposed super-root dispute games and OPCM v8.0.0
The governance proposal described an L1 contract upgrade and a September 24 target that was pending approval and soak at publication; this snapshot does not infer execution from the target date.
- Type:Proposal
- Proposal:Proposed at source publication
- Release:Release candidate evidence cited
- Activation:Not asserted by this snapshot
Sources: Optimism Collective — Upgrade 20 - Super Root Dispute Games & OPCM v8.0.0 (external site) · OP Labs — Optimism monorepo releases (external site)
-
Karst activation recorded for OP Mainnet
The reviewed OP Mainnet registry configuration records Karst at 2026-07-08T16:00:01Z.
- Type:Upgrade
- Proposal:Approved before registry activation
- Release:Activation config recorded
- Activation:Activated mainnet
Source: OP Labs — OP Mainnet registry configuration (external site)
Publication date unknown
-
OP Stack interop rollout required specialized node preparation
The official preparation notice describes a testnet dependency set and specialized client topology, but its late-July 2026 OP Mainnet target has passed without evidence of activation, and the Lagoon hardfork documentation reviewed on September 26 lists it as not scheduled. It does not establish OP Mainnet activation.
- Type:Roadmap
- Proposal:Documented rollout
- Release:Time sensitive notice
- Activation:Op mainnet not established
Source: Optimism — Prepare for interop on OP Sepolia and Unichain Sepolia (external site)
-
Lagoon remained in development with no default activation scheduled
Optimism documentation identifies Lagoon as the upcoming interop hardfork, marks it in development, and records no Superchain-wide mainnet or Sepolia activation defaults. The specification is subject to change and this record does not claim activation on OP Mainnet.
- Type:Roadmap
- Proposal:In development
- Release:Specification subject to change
- Activation:Mainnet not scheduled
Sources: Optimism — Lagoon network upgrade (external site) · Optimism — Prepare for interop on OP Sepolia and Unichain Sepolia (external site)
Topics your AI can explain
Your AI can explain these topics for OP Mainnet through the connection, with sources.
Known gaps
What this profile's review did not establish:
- The entity operating the OP Mainnet sequencer and batcher was not named in the reviewed pages; the privileged-roles page defers to the Superchain Registry.
- The exact airgap length and whether the one-week challenge period is currently 3.5 plus 3.5 days were not captured; the fault-proofs explainer names an airgap window without a length, and the Standard Bridge page states about 7 days overall.
- Upgrade 20 (super-root dispute games, OPCM v8.0.0) was proposed with a September 24 target; its approval and execution on OP Mainnet were not verified, and it may change the proof configuration described here. It does not enable interop either way.
- Whether the Deputy Guardian or the permissioned fallback has been used again since the 2024 Granite episode was not verified.
- Node storage figures are dated June 2025 in Optimism's docs; current size was not measured.
- Ledger support rests on a templated Ledger coin page plus Ledger Wallet code that keeps the Optimism network behind a switch that is off by default; the remote switch setting and Ledger's support site could not be read, so the native Ledger rating is lower confidence.
- No scaling options anchored to OP Mainnet (L3 rollups or channels) were reviewed, so this profile lists none.
- Atomic-swap, light-client and algorithmic-stablecoin surfaces were not reviewed; the Safe Recovery Module was checked only against Safe's network listing, not tested on OP Mainnet.
- Third-party bridges and AMM venues other than Uniswap v3 were not reviewed; a Velodrome docs page did not load usable content.
Sources
Oldest dated source check: Source checked Sep 25, 2026 Next check due Oct 25, 2026.
- Connecting to OP Mainnet (external site)
- The OP Stack (external site)
- op-node README (external site)
- Fault proofs explainer (external site)
- Using the Standard Bridge (external site)
- Privileged roles in OP Stack chains (external site)
- Running a node from source (external site)
- OP Mainnet registry configuration (external site)
- Upgrade 20 - Super Root Dispute Games & OPCM v8.0.0 (external site)
- Smart Account Supported Networks (external site)
- Optimism Deployments (Uniswap v3) (external site)
- USDC Contract Addresses (external site)
- Optimism wallet (external site)
- Optimism wallet (external site)
- Upgrade Proposal #10: Granite Network Upgrade (external site)
- OP Mainnet (external site)
- Forced Transaction (external site)
- ledger-live: coin-module loaders (list of networks Ledger Wallet can add) (external site)
- ledger-live: currencyOptimism feature switch (external site)
- ledger-live: feature-flag defaults (a switch declared with no value is off) (external site)
- ledger-live: useCurrenciesUnderFeatureFlag (hides networks whose feature switch is off) (external site)
- trezor-suite: Ethereum-style network configuration (develop branch) (external site)
- OP Mainnet (ETH) Blockchain Explorer (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding