Layer 2 blockchain · settles to Ethereum
Scroll ticker SCR
Summary
Zero-knowledge rollup on Ethereum. A single centralized sequencer orders transactions into L2 blocks (3-second target, best effort) and a rollup relayer commits batch data to Ethereum as blobs. Provers generate validity proofs with an OpenVM RISC-V zkVM (STARK proofs wrapped in a SNARK for on-chain checking); a verifier contract on Ethereum must accept the proof before a batch's state root and withdrawal root are finalized. Since the Euclid upgrade (April 2025) users can force transactions in from Ethereum and anyone can submit and finalize batches if the operator stops; L2BEAT says both paths open only after 7 days without finalization. Block production uses no stake or work of its own. 12569101126
Design
- System
- Layer 2 blockchainScroll Mainnet (chain ID 534352) is a zero-knowledge (validity-proof) rollup on Ethereum, not an optimistic rollup. ETH is the gas asset; SCR is an ERC-20 governance token and does not pay gas. The team announced in September 2026 a plan to turn the public chain into a private, permissioned, application-specific network; if that happens this classification must be reviewed again.
- Settles to
- EthereumBatch data is posted to Ethereum as blobs and a batch is final once an Ethereum verifier contract accepts its validity proof. Withdrawals are then executed on Ethereum with a Merkle proof against the finalized withdrawal root; there is no fraud-proof challenge window, but Scroll publishes no fixed proof-to-finality time, and Scroll said its 2026 prover upgrades would pause finalization for about an hour each. Forced inclusion and permissionless batch submission open after 7 days, per L2BEAT.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One centralized, privileged sequencer, according to L2BEAT. Scroll's docs do not name its operator, though its fees go to a Scroll-maintained fee vault and the gas-price oracle is updated by a relayer run by Scroll. Since Euclid the authorized block signer is read from a system config contract on Ethereum, replacing the earlier proof-of-authority (Clique) setup. A coordinator dispatches proving jobs to a pool of provers; L2BEAT says users can run the source-available prover to submit proofs if the operator fails.
- Fork choice
- No open L2 fork choice: sequencer blocks are canonical, Scroll documents a maximum reorg depth of 17 L2 blocks since the DarwinV2 upgrade, and the only absolute guarantee comes when a batch's validity proof is verified on Ethereum.
Qualifications
- Scarce resource · Not applicable. Scroll block production uses no stake or work of its own; the sequencer is an operator-assigned signer and security comes from Ethereum plus validity proofs.
- Finality · Partial. Scroll documents three stages: Confirmed (in a sequencer block), Committed (batch data included on Ethereum) and Finalized (validity proof verified on Ethereum). Only the last is an Ethereum-backed guarantee; before it, reorgs of up to 17 L2 blocks are possible.
- Upgrade authority · Contested. Scroll's upgrade and governance docs still describe a 9-of-12 Security Council and a two-week upgrade timelock, while an April 2026 forum proposal and L2BEAT describe a 3-of-4 team admin multisig in control since 2026-06-01, with an emergency path that has no delay.
- Public network continuity · Unknown. Mainnet was still operating as a public chain at review time, but Scroll plans a transition to a permissioned chain: indicative dates are an SCR and USX deployment on Ethereum in November to December 2026, a governance vote by end of 2026 and the chain change in early 2027. None of these dates are final.
- Public testnet · Not applicable. Scroll's docs say the Scroll Sepolia testnet was shut down after 2026-07-30; no replacement public testnet is named.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Decentralized operation and upgrade safety: one centralized sequencer orders all transactions, forced inclusion only opens after 7 days, and since June 2026 a 3-of-4 team multisig can upgrade the core contracts with no exit window, per L2BEAT. The team also plans to move the chain to a permissioned model.The security emphasis means state transitions are checked by validity proofs on Ethereum and all data is posted there. That guarantee depends on sound circuits and verifiers: 2026 saw an emergency fix for a prover bug and several OpenVM security advisories, and instantly upgradable contracts let the key holders change the rules.
- Full node at home
- Demanding 7101213Scroll's node guide recommends a machine comparable to an AWS t3.2xlarge instance and a 4 TB SSD, because the archive snapshot is nearly 2 TB; only an archive snapshot is documented. A node also needs a fully synced Ethereum mainnet RPC and a blob data source (a beacon supernode, Blobscan or Scroll's S3 bucket). Scroll says it is moving node operators from its Geth fork to a Reth-based node.
- 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 Scroll 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 | Built into the protocolLimited scope | Scroll's rollup protocol produces what a light verifier checks: once a batch is finalized, its state root on Ethereum is backed by a validity proof, and since Euclid the state uses Ethereum's Merkle-Patricia trie format, so anyone following Ethereum can verify Scroll account and storage proofs against that root. Limited: only finalized batches can be checked this way, and no dedicated Scroll light client was reviewed. 123 |
| 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 Scroll was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Scroll runs EVM contracts with standard Ethereum tooling and added EIP-7702 and RIP-7212 (support for passkey signatures) in Euclid. SELFDESTRUCT is disabled and a few opcodes differ. 56 |
| 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 to cancel or delay a sent payment or to recover an account was found. Scroll supports EIP-7702 smart-account features, which wallets could use for recovery, but no recovery product live on Scroll was reviewed. 6 |
| Rollups | Unknown | Rollups anchored to Scroll were not reviewed. Scroll 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 | Established in the ecosystemSyncSwap, Uniswap v3, Ambient | Scroll's developer ecosystem page lists DEX deployments including Ambient, SyncSwap, HonneyPop, Uniswap v3, iZUMi and SushiSwap; SyncSwap's own docs list its Scroll pool factories, vault and routers. Liquidity depth and current activity were not measured, and the planned move to a permissioned chain may affect these venues. 1727 |
| Issuer-native stablecoins | First-partyUSX (USX.Capital) | USX is a dollar stablecoin built on Scroll that Scroll's forum lists as part of its own product stack. Its docs say it is fully collateralized; institutional partners can redeem 1:1 for USDC directly (up to 14 days), while other holders exit through market swaps. Its contracts are on Scroll, and Scroll plans to deploy USX on Ethereum mainnet. USDC on Scroll is not Circle-issued: Circle's native USDC address list does not name Scroll, and Scroll's audit list includes a USDC bridge gateway. 182223282930 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Scroll were not reviewed. USX describes itself as fully collateralized rather than algorithmic, but its yield strategies were not audited here. |
| Bridges | Native to the protocolScroll canonical bridge (gateway router, gateways and Scroll Messenger), Enforced transaction gateway on Ethereum | ETH, ERC-20, NFT and message transfers between Ethereum and Scroll run through protocol contracts; withdrawals execute on Ethereum with a Merkle proof, submitted by the user or a third party, after the batch is finalized. Scroll's developer ecosystem page also lists third-party routes (LI.FI, Across, Stargate, Rhino, Squid); Across's current chain list does not show Scroll, and the others were not checked. Risk: Bridge safety rests on the soundness of the zkVM prover and verifier (patched in an emergency in February 2026) and on a 3-of-4 team multisig that can upgrade the contracts instantly with no exit window, per L2BEAT. Forced exits via Ethereum open only after 7 days, and the planned permissioned transition has no published migration path yet. 1415161722252631 |
| Block explorers | ThinScrollscan (served by Blockscout software) | Scroll's developer page names Scrollscan as the mainnet explorer. At review time scrollscan.com was served by Blockscout software, and Blockscout's own Scroll address (scroll.blockscout.com) redirected there, so these are one explorer, not two. Other explorers were not checked. The Scroll rollup scanner linked from the docs returned 404. Explorer indexes are not canonical consensus. 1334 |
| Hardware wallets | ThinTrezor Safe 3, 5 and 7 (through MetaMask or Rabby), Ledger Wallet (Scroll behind a default-off feature switch) | See custody rows: Trezor lists the Scroll network and SCR but says Trezor Suite does not support Scroll and points users to MetaMask or Rabby; Ledger Wallet's code has a Scroll network behind a feature switch that is off by default, and no Ledger page confirms users can open it. 323336 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | PartialSame as native: Unknown | Can: Possibly add a Scroll account in Ledger Wallet: Ledger's current wallet code includes Scroll as an Ethereum-family network, but behind a feature switch that is off by defaultCounted as limited first-party support under the shared custody rule: Ledger Wallet hides Scroll unless its feature switch is on, the switch is off by default in code, and Ledger's remote switch setting could not be read. No readable Ledger page confirms it is on for users: Ledger's Scroll coin page returned 404 and its supported-assets page did not name Scroll. Device models and SCR token handling were not reviewed. 33353637 |
| Trezor | Through an intermediaryMetaMask or Rabby (third-party wallet apps named by Trezor)Same as native: Unknown | Can: Send and receive assets on the Scroll network with a Trezor Safe 3, Safe 5 or Safe 7, confirming each transaction on the device, through MetaMask or Rabby Can: Hold SCR, which Trezor's Scroll page names Cannot: Use Trezor Suite for Scroll: Trezor's Scroll page captions its screenshot as not supported in the Trezor Suite appTrezor's page lists Scroll as a supported network for the Safe models; older models and contract-interaction coverage were not reviewed. 32 |
Public data
iKnow Blockchain has no public-data lookups for Scroll 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
-
Scroll announced a prover upgrade to OpenVM v2.0.0 with a new verifier contract
Scroll announced moving its prover from OpenVM v1.6.0 to v2.0.0, which moves to a new proof system called SWIRL and includes three security fixes from OpenVM v1.7.0, two of them in the Solidity verifier wrapper. A new verifier contract was deployed on Ethereum, the mainnet switch was scheduled for 22 September 2026 with finalization paused for about an hour, and a Scroll reply on the thread that day said the upgrade had been executed.
- Proposal:announcement only; no DAO vote required per Scroll
- Implementation:new mainnet verifier address published
- Release:OpenVM v2.0.0; Scroll monorepo tag v4.8.0 (prover and coordinator code) published 2026-09-22 13:44 UTC
- Activation:executed on mainnet on 2026-09-22, per a Scroll reply on the announcement thread
Sources: Scroll Governance Forum — Announcement: OpenVM v2.0.0 Upgrade on Scroll (external site) · Scroll (GitHub) — v4.8.0 (external site)
-
Scroll team outlined a plan to move the chain to a private, permissioned network
In a forum update the Scroll team said it plans to transition Scroll from a general-purpose public network into a private, application-specific network designed around its AI products, gradually over about nine months. SCR would move to Ethereum mainnet with no change to its supply or tokenomics and would remain the governance token. A later DAO update called the target a permissioned chain and gave indicative dates running from late 2026 to early 2027.
- Proposal:direction announced; formal DAO proposal not yet posted
- Implementation:migration details still under discussion; no migration path published
- Release:indicative: SCR and USX contracts on Ethereum mainnet from mid-November to December 2026
- Activation:not active; chain transition targeted for early 2027
Sources: Scroll Governance Forum — What We've Been Working On at Scroll (external site) · Scroll Governance Forum — Scroll DAO Monthly Update, September 2026 (external site)
-
Scroll proposed ending its Security Council in favor of a Scroll admin multisig
A Scroll-led forum post proposed dissolving the independent Security Council and moving protocol admin control to a Scroll admin multisig, citing cost relative to use, and wound down four DAO contributor roles. L2BEAT records the change as executed on 1 June 2026, with a 3-of-4 team multisig replacing the 9-of-12 council.
- Proposal:Scroll-led proposal posted 2026-04-13
- Implementation:executed on Ethereum on 2026-06-01 according to L2BEAT
- Release:governance change; no software release
- Activation:active according to L2BEAT
Sources: Scroll Governance Forum — Governance Update: Security Council Transition, Contributor Roles & Operational Adjustments (external site) · L2BEAT — Scroll (external site)
-
Report on the 23 February 2026 emergency prover upgrade
A bug bounty report found that Scroll's zkVM prover skipped a subgroup check on one kind of curve point in the ecPairing precompile, so some inputs gave different results in the sequencer and the prover and could have stopped batches from finalizing. The Security Council deployed a patched prover as an emergency upgrade on 23 February 2026 and published the fix and this report afterward.
- Implementation:patched prover release v0.7.2
- Release:patch published in the public repository after deployment
- Activation:deployed on mainnet 2026-02-23
Source: Scroll Governance Forum — Report: Scroll Mainnet Emergency Upgrade on 2026-02-23 (external site)
Topics your AI can explain
Your AI can explain these topics for Scroll through the connection, with sources.
Known gaps
What this profile's review did not establish:
- The operator of the Scroll sequencer and the identities of the four admin multisig signers were not sourced; L2BEAT calls the sequencer centralized and the multisig a Scroll team multisig, and Scroll's forum only calls it a Scroll Admin multisig.
- Scroll's own docs still describe the 9-of-12 Security Council and a two-week upgrade timelock; the June 2026 change to a 3-of-4 team multisig is sourced to L2BEAT and the April 2026 forum proposal, not to an updated Scroll page.
- No typical time from transaction to proof-verified finality on Ethereum was found in Scroll's docs or on the L2BEAT page as read.
- The migration path for users and apps if the chain becomes permissioned, and whether public withdrawals will stay open, is not yet published.
- Current chain size and bandwidth needs for a full node were not captured beyond Scroll's archive-snapshot guidance; the Reth-based node's requirements were not reviewed.
- Ledger Wallet's code has a Scroll network behind a feature switch that is off by default; whether Ledger has switched it on for users could not be confirmed (coin page 404, not named on the supported-assets page, remote switch settings not public).
- Trezor Suite support for Scroll and coverage of older Trezor models were not confirmed.
- Third-party bridges other than Across (LI.FI, Stargate, Rhino, Squid) were not checked for current Scroll support.
- DEX liquidity depth, Scroll Swap (swap.scroll.io) and whether listed DEXes remain active on Scroll were not reviewed.
- USX reserve composition, audits and redemption limits were not independently reviewed; only its own docs were read.
- Atomic-swap, reversible-transfer, account-recovery, channel and algorithmic-stablecoin surfaces on Scroll were not reviewed.
- Scroll's public status page now says it was deleted and the rollup scanner link returns 404, so live health data from Scroll itself was not available.
- Block explorers other than Scrollscan (for example OKLink or other indexers) were not checked; the former Blockscout address now redirects to Scrollscan.
- How the Scroll base fee is set and whether any part of it is burned is not stated in Scroll's fee or Curie docs; the docs say only that all fees go to a Scroll-maintained fee vault.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Rollup Process (external site)
- Transactions (external site)
- Accounts and State (external site)
- Blocks (external site)
- Ethereum and Scroll Differences (external site)
- Euclid Upgrade (external site)
- Galileo Upgrade (external site)
- Scroll Upgrades (external site)
- Proof Generation (external site)
- Execution Node (external site)
- Transaction Fees on Scroll (external site)
- Running a Scroll Node (external site)
- Developers (network configuration and FAQ) (external site)
- L1 and L2 Bridging (external site)
- Withdraw Gateways (external site)
- Enforced Transactions (external site)
- Developer Ecosystem (external site)
- Audits and Bug Bounty (external site)
- Governance Technical Architecture (external site)
- What is the Security Council? (external site)
- Governance Update: Security Council Transition, Contributor Roles & Operational Adjustments (external site)
- What We've Been Working On at Scroll (external site)
- Scroll DAO Monthly Update, September 2026 (external site)
- Announcement: OpenVM v2.0.0 Upgrade on Scroll (external site)
- Report: Scroll Mainnet Emergency Upgrade on 2026-02-23 (external site)
- Scroll (external site)
- Smart Contracts (external site)
- What is USX? (external site)
- Smart Contract Addresses (external site)
- USDC Contract Addresses (external site)
- Chains & Contracts (external site)
- Scroll wallet (external site)
- Supported crypto assets (external site)
- Scroll blockchain explorer (Scrollscan) (external site)
- Ledger Wallet coin-module loaders (loaders.ts, develop branch) (external site)
- Ledger Wallet feature switch currencyScroll (develop branch) (external site)
- Ledger feature-flag definitions (define.ts): a switch declared with no value is off by default (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