Layer 2 blockchain · settles to Ethereum
Zora Network ticker ETH
Summary
Optimistic rollup on Ethereum built from the OP Stack. One sequencer orders transactions into 2-second blocks, and a batcher posts the transaction data to Ethereum as blobs, so anyone following Ethereum can check new blocks without trusting the sequencer; Ethereum deletes blob data after about 18 days, so older history also needs a snapshot or archive. One permissioned proposer posts state claims to Ethereum through dispute games, and only Conduit's multisig may challenge them. L2BEAT says, and a read of the latest game on Ethereum confirmed, that the game holds a placeholder instead of the fault-proof program's starting state, so disputes cannot be settled by re-executing the chain and withdrawals rely on the proposer and challenger acting honestly. Users can force a transaction in through Ethereum, with up to about a 12-hour delay. Block production uses no stake or work of its own. 11314151618
Design
- System
- Layer 2 blockchainZora Network (chain ID 7777777) is an OP Stack optimistic rollup operated by Conduit that posts all transaction data to Ethereum. ETH pays gas. The ZORA token lives on Base and Solana, not on Zora Network, and Zora says it carries no governance rights, so the name uses ETH. L2BEAT groups Zora with 'Others' rather than rollups because its fraud-proof system is not functional; it keeps the Layer 2 class because its data, bridge and withdrawals are anchored to Ethereum.
- Settles to
- EthereumAll transaction data is posted to Ethereum as blobs. OP Stack blocks are final once the Ethereum block holding their data is finalized; in two checks during review Zora's finalized head trailed its latest block by about 68 and 37 minutes. Withdrawals wait 7 days after being proven, per the Ethereum contract setting, and L2BEAT lists a 3.5-day state-root challenge period. They depend on one permissioned proposer and a 4-of-11 Conduit multisig that can upgrade the contracts with no delay.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One sequencer. Optimism's September 2026 governance proposal says Conduit operates Zora, and Zora's own docs say Zora deployed the network software but does not operate the network. L2BEAT lists one permissioned proposer address, a 2-of-10 Zora multisig that can change the batcher address and gas settings, and the Conduit multisig as the only party allowed to challenge.
- Fork choice
- No open L2 fork choice: the sequencer's blocks are canonical, and the sequencer can still reorganize them until their data lands on Ethereum; after that the chain is derived from Ethereum data, and Ethereum's own finality governs it. Fraud-proof challenges do not reorganize the chain; they only affect bridge withdrawals.
Qualifications
- Scarce resource · Not applicable. Zora block production uses no stake or work of its own; the sequencer is assigned by the operator, and security comes from Ethereum data availability plus the permissioned proposer and challenger.
- Finality · Partial. OP Stack chains have three stages: unsafe (in a sequencer block, which the sequencer can still reorganize), safe (data posted to Ethereum) and finalized (the Ethereum block holding the data is final). Only the last inherits Ethereum finality.
- Fraud proofs · Partial. Dispute-game contracts are deployed on Ethereum and a new state claim is posted regularly, but only one permissioned proposer can post and only the Conduit multisig can challenge. L2BEAT says the game holds a placeholder where the fault-proof program's starting state should be, which a read of the latest game on Ethereum confirmed, so no dispute can be resolved by execution; L2BEAT rates Zora below Stage 0.
- Upgrade authority · Applies. A read of the Ethereum contracts during review showed the admin contract owner, the dispute-game factory owner and the pause guardian set to a 4-of-11 Conduit Safe, matching the Optimism proposal and L2BEAT. The Superchain Registry file for Zora still marks it as governed by Optimism with the old owner address, so it lags the chain.
- Network status · Applies. Zora Network was producing blocks at review time and no sunset or migration notice was found on zora.energy, Zora's docs or Zora's help centre. Zora's own app now runs on Base, Robinhood Chain and Solana, the ZORA token exists only on Base and Solana, the network docs sit on a site Zora labels legacy, and on-chain trading activity is very low.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Decentralized operation and withdrawal security: one operator-run sequencer orders every transaction, one permissioned proposer posts state claims, the fraud-proof game cannot settle a dispute by execution, and a 4-of-11 Conduit multisig can upgrade the Ethereum contracts at once with no exit window, per L2BEAT and a read of the contracts.Posting all transaction data to Ethereum and the roughly 12-hour forced-inclusion path are the Ethereum-derived protections that remain. The upgrade keys held under Optimism governance moved to Conduit in September 2026, so Zora no longer shares the Superchain's governance safeguards.
- Full node at home
- Unknown 212234Conduit's generic node repository for its OP Stack chains asks for at least 4 cores, 16 GB RAM and a 500 GB SSD (8+ cores, 32 GB and a 1 TB+ NVMe recommended), runs op-reth as an archive node and needs Ethereum RPC and beacon endpoints: consumer-class hardware. Whether an outsider can run one is not established: Conduit says the chain operator must switch on external nodes, which was not confirmed for Zora, and that self-hosted nodes are outside its standard support.
- 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 Zora Network was not reviewed; EVM contracts could implement hash-locked swaps, but none was verified. |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Unknown | No Zora Network light client was reviewed. State claims on Ethereum come from one permissioned proposer and cannot be disputed by execution, so checking Zora state against them would trust that proposer. |
| 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 Zora Network was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Zora Network runs the EVM with the OP Stack's Bedrock design, which Zora's docs say mimics Ethereum as closely as possible, so spend conditions are written as smart contracts; Seaport, Safe and Zora's NFT factories are deployed there. Karst added the per-transaction gas cap in July 2026. 3520 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; no protocol feature for reclaiming, cancelling or delaying a payment, or for regaining control without a lost key, was found on Zora Network. Zora's deployments page lists Safe multisig contracts, but a plain multisig threshold does not meet part (b), and no Safe delay or recovery module on Zora Network was reviewed. 5 |
| Rollups | Unknown | Chains that settle to Zora Network were not reviewed. Zora Network itself is a rollup on Ethereum; its settlement is described in the mechanism and Ethereum dependency notes. |
| 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 | ThinUniswap v3, Uniswap v2, Uniswap v4 | Uniswap's developer docs list a full Uniswap v3 deployment on Zora, and DefiLlama tracks Uniswap v2, v3 and v4 there. DefiLlama recorded almost no DEX trading volume on Zora in the 30 days before review, so venues exist but activity is minimal. Liquidity depth was not measured. 2526 |
| Issuer-native stablecoins | None found | No issuer-native stablecoin was found on Zora Network: Circle's native USDC list and Tether's supported-protocol list do not name Zora. Any stablecoins on Zora would be bridged copies; their contracts and backing were not reviewed. 2728 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Zora Network were not reviewed. |
| Bridges | Native to the protocolZora canonical bridge (OP Stack standard bridge, via Superbridge), Relay, Decent, Across | Zora's docs name bridge.zora.energy as the official native bridge and say ETH deposits show up in about 1 to 2 minutes; the bridge page routes native bridging through Superbridge and lists Relay, Decent and Across as third-party instant bridges. Withdrawals through the canonical bridge wait 7 days after being proven. Risk: Canonical withdrawals depend on one permissioned proposer, and L2BEAT says disputes cannot be settled by execution. A 4-of-11 Conduit multisig can upgrade the bridge contracts instantly with no exit window. The third-party bridges are separate trust models, and Zora's bridge page says Zora is not responsible for losses or delays when using them. 461314 |
| Block explorers | ThinConduit Explorer (explorer.zora.energy) | Zora's network page and the Superchain Registry name explorer.zora.energy, which is Conduit's lightweight explorer that reads straight from the chain's RPC without a separate index. The former Blockscout address for Zora now redirects there; Routescan's Zora pages refused automated access and were not checked. Explorer views are not canonical consensus. 2152324 |
| Hardware wallets | ThinTrezor Safe 3, 5 and 7 (through MetaMask or Rabby) | See custody rows: Trezor's Ethereum page lists Zora among supported networks, but Trezor Suite's own network list does not include it, so use goes through MetaMask or Rabby; Ledger Wallet's code has no Zora network. 293233 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | UnknownSame as native: Unknown | Ledger Wallet's current code has no Zora network, Ledger's Zora coin pages returned 404, and the fetched copy of Ledger's supported crypto assets page did not mention Zora. Whether a Ledger can sign Zora transactions through a third-party wallet was not verified. 3132 |
| Trezor | Through an intermediaryMetaMask or Rabby (third-party wallet apps named by Trezor)Same as native: Unknown | Can: Use ETH on the Zora network with a Trezor Safe 3, Safe 5 or Safe 7 through MetaMask or Rabby; Trezor's Ethereum page lists Zora among its supported networks Cannot: Manage Zora network accounts in Trezor Suite itself: Suite's current network list does not include ZoraTrezor's Ethereum page names Trezor Suite, MetaMask and Rabby without tying them to networks. Because Trezor Suite's current network code has no Zora entry, the working path is a third-party wallet. Trezor's separate ZORA token page lists only Base, because the token is not deployed on Zora Network. Older models and contract interactions were not reviewed. 293033 |
Public data
iKnow Blockchain has no public-data lookups for Zora Network yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Optimism governance transferred Zora Network's admin keys to Conduit
An Optimism maintenance upgrade proposal moved ownership of Zora Network's Ethereum-side admin contract, dispute-game factory and Zora-side admin contract from an Optimism-controlled safe to a Conduit safe, ending Optimism governance of Zora. L2BEAT records the change as executed on 16 September 2026 and now lists a 4-of-11 Conduit multisig that can upgrade the contracts instantly.
- Proposal:maintenance upgrade proposal posted 2026-09-02 under the standard veto period
- Implementation:ownership transferred, per L2BEAT and a read of the Ethereum contracts
- Release:not a software release
- Activation:active since 2026-09-16, per L2BEAT
Sources: Optimism Collective governance forum — Maintenance Upgrade Proposal: Mode, Metal, Zora, and Dust Ownership Transfer to Conduit (external site) · L2BEAT — Zora Network (external site)
-
Karst hard fork (OP Stack Upgrade 19) activated on Zora Network
Zora was among the OP Stack chains named for the Karst upgrade. Karst added a subset of Ethereum's Osaka changes on the L2, including a per-transaction gas cap of 16,777,216 gas and a tighter limit on one cryptographic precompile, and required node operators to move from op-geth to op-reth. Karst also promoted a new fault-proof game type on OP Stack chains, but L2BEAT records that Zora stayed on its permissioned dispute game.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in OP Stack releases
- Release:op-node and op-reth releases named in the notice
- Activation:active on Zora Network since 2026-07-08
Sources: Optimism Docs — Upgrade 19: Karst hard fork (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/zora.toml (external site) · L2BEAT — Zora Network (external site)
-
Jovian hard fork (OP Stack Upgrade 17) activated on Zora Network
Zora was among the chains named for the Jovian upgrade. Jovian let operators set a minimum base fee, added a default in-protocol limit on each block's estimated Ethereum data use, and changed how the operator fee is calculated.
- Proposal:Optimism governance upgrade proposal
- Implementation:shipped in OP Stack releases
- Release:OP Stack node releases
- Activation:active on Zora Network since 2025-12-02
Sources: Optimism Docs — Upgrade 17: Jovian hard fork (external site) · Optimism (ethereum-optimism/superchain-registry) — Superchain Registry: mainnet/zora.toml (external site)
Topics your AI can explain
Your AI can explain these topics for Zora Network through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Zora Network documentation now sits on a site Zora labels legacy and has no node-running, fee-configuration or withdrawal-time page; several facts here come from Optimism, Conduit, L2BEAT and direct reads of the chain instead.
- The Superchain Registry file for Zora still marks it as governed by Optimism with the old owner address; when it will be updated, and whether Zora will keep receiving future OP Stack upgrades now that OP Labs support has ended, is not published.
- The identities of the eleven Conduit multisig signers, the ten Zora multisig signers and the operator of the proposer address were not sourced.
- The placeholder in the dispute game is sourced to L2BEAT and was confirmed by a read of the latest game on Ethereum, but no Optimism, Conduit or Zora page describing it was found.
- Ethereum deletes blob data after about 18 days; who keeps an archive of Zora's older batch data, and whether snapshots are available to people outside Conduit, was not reviewed.
- Whether Conduit has enabled external self-hosted nodes for Zora Network was not confirmed, so the home-node posture is unknown even though the published generic hardware is consumer-class.
- No official statement was found on the long-term future of Zora Network now that Zora's own app and token have moved to other chains; the network status page refused automated access.
- Node requirements come from Conduit's generic repository for all its OP Stack chains; Zora's current chain size and bandwidth needs were not published.
- Ledger support for the Zora network was not verified: Ledger Wallet's code has no Zora network, coin pages returned 404, and Zora was not found in the fetched supported-assets page.
- The Trezor rating rests on Trezor Suite's current network code, which has no Zora entry; Trezor's pages do not tie wallet apps to networks.
- Bridged stablecoins on Zora Network, and the current Zora support of Relay, Decent and Across, were not checked.
- Routescan's Zora explorer refused automated access and was not checked.
- Atomic-swap, reversible-transfer and recovery, light-client, channel, chains settling to Zora and algorithmic-stablecoin surfaces were not reviewed; no throughput claims were recorded.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Zora Network: Introduction (external site)
- Zora Network: Network (external site)
- Zora Network: ETH vs ZORA (external site)
- Zora Network: Bridging (external site)
- Zora Network: Deployments (external site)
- Zora Bridge (external site)
- ZORA (Zora Network site) (external site)
- Coins Protocol (external site)
- Creating a Coin (external site)
- What is the $ZORA Contract Address? (external site)
- Tokenomics (external site)
- What has changed on Zora? (external site)
- Zora Network (external site)
- Maintenance Upgrade Proposal: Mode, Metal, Zora, and Dust Ownership Transfer to Conduit (external site)
- Superchain Registry: mainnet/zora.toml (external site)
- Transaction finality (external site)
- Transaction fees (external site)
- Danksharding (external site)
- Upgrade 17: Jovian hard fork (external site)
- Upgrade 19: Karst hard fork (external site)
- Run an OP Stack Node (external site)
- conduitxyz/conduit-optimism-external-node (external site)
- Conduit Explorer (external site)
- Zora | Explorer (external site)
- Zora Deployments (Uniswap v3) (external site)
- DEX overview for Zora (API) (external site)
- USDC Contract Addresses (external site)
- Supported Protocols (external site)
- Ethereum wallet (external site)
- Zora wallet (ZORA token) (external site)
- Supported crypto assets (external site)
- ledger-live: coin-module loaders (list of networks Ledger Wallet can add) (external site)
- trezor-suite: Ethereum-style network configuration (develop branch) (external site)
- Spin up your own Ethereum node (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