Search

Search for projects by name

Recategorisation happening in
Learn more
SummaryValue SecuredActivityOnchain costsLivenessMilestones & IncidentsRisk summaryRisk analysisRollup stageData availabilityState derivationState validationOperatorWithdrawalsPermissionsSmart contracts

Linea logoLinea

Badges

About

Linea is a ZK Rollup powered by a zkEVM developed at Consensys, designed to scale the Ethereum network.

Value secured
$369.95 M1.81%
Canonically Bridged
$247.39 M
Natively Minted
$30.34 M
Externally Bridged
$92.21 M
View TVS Breakdown
  • Tokens
  • Past day UOPS
    0.972.74%
  • Gas token
    ETH
  • Stage
  • Type
    ZK Rollup
  • Purpose
    Universal
  • Chain ID
    59144
    • Sequencer failureState validationData availabilityExit windowProposer failure
    Explore more in Discovery UI

    Badges

    About

    Linea is a ZK Rollup powered by a zkEVM developed at Consensys, designed to scale the Ethereum network.

    Value Secured

    2024 Jun 14 — 2025 Jun 14

    Total value securedTotal
    $369.95 M1.81%
    Canonically BridgedCanonically Bridged ValueCanonical
    $247.39 M2.49%
    Natively MintedNatively Minted TokensNative
    $30.34 M4.75%
    Externally BridgedExternally Bridged ValueExternal
    $92.21 M2.29%
    View TVS breakdown
    Activity

    2024 Jun 14 — 2025 Jun 13

    Onchain costs

    The section shows the operating costs that L2s pay to Ethereum.

    2024 Jun 14 — 2025 Jun 13

    1 year total cost
    $134.04 K
    Avg cost per L2 UOP
    $0.001288
    1 year data posted
    3.58 GiB
    Avg size per L2 UOP
    110.66 B
    Liveness

    The chart illustrates how "live" the project's operators are by displaying how frequently they submit transactions of the selected type and if these intervals deviate from their typical schedule.

    2025 May 15 — Jun 13

    30D avg. tx data subs. interval
    1 hour
    30D avg. proof subs. interval
    3 hours
    30D avg. state updates interval
    3 hours
    Past 30 days anomalies
    Milestones & Incidents

    Proof system is complete

    2024 Jun 9th

    The Linea proof system and verifier on ethereum covers 100% of the zkEVM.

    Learn more

    Linea starts using blobs

    2024 Mar 26th

    Linea starts publishing data to blobs.

    Learn more
    Risk summary
    The circuit of the program being proven is not public.

    Funds can be frozen if

    1. the sequencer refuses to include an exit transaction (CRITICAL),
    2. the operator censors withdrawal transaction.

    Users can be censored if

    1. the operator refuses to include their transactions.

    MEV can be extracted if

    1. the operator exploits their centralized position and frontruns user transactions.
    Risk analysis
    The circuit of the program being proven is not public.
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    No mechanism

    There is no mechanism to have transactions be included if the sequencer is down or censoring. Eventually (after 6 months of no finalized blocks) the Operator role becomes public, theoretically allowing anyone to post data.

    State validation
    ZK proofs (SN)

    SNARKs are zero knowledge proofs that ensure state correctness, but require trusted setup.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1. Unlike most ZK rollups, transaction data is posted instead of state diffs.

    Exit window
    None

    There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.

    Proposer failure
    Cannot withdraw

    Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen. Eventually (after 6 months of no finalized blocks) the Operator role becomes public, theoretically allowing anyone to propose state with valid proofs.

    Rollup stageLineaLinea is a
    Stage 0
    ZK Rollup.

    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.
    Data availability

    All data required for proofs is published on chain

    All the data that is used to construct the system state is published on chain in the form of cheap blobs or calldata. This ensures that it will be available for enough time.

    1. LineaRollup.sol - Etherscan source code, submitBlobs() function
    Learn more about the DA layer here: Ethereum logoEthereum
    State derivation
    Node software

    The node software (Linea Besu) and a guide to reconstruct the state from L1 is available here. Other node implementations like Nethermind, Geth or Erigon can sync too, but state derivation from L1 and Linea-specific features are unsupported.

    Compression scheme

    Linea uses a bespoke lossless compression scheme based on LZSS (deflate-like). It is available as a dedicated library and a zk-decompression circuit in Gnark.

    Genesis state

    Is available via the official Linea docs for Linea Besu (preloaded), Besu, Erigon, Nethermind, Geth.

    Data format

    Linea groups L2 blocks into batches which are then posted to L1 for proving. Each batch (whether sent as a blob or compressed calldata) contains L2 blocks. Blocks in turn include the transactions with unnecessary data stripped. More info on the compression, packing and blob structure.

    State validation

    Each update to the system state must be accompanied by a ZK proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. These proofs are then verified on Ethereum by a smart contract.

    Prover Architecture

    The Linea prover code is available on Github. Linea splits proving into: Corset (Go + Lisp DSL) expands EVM execution traces and generates a bespoke constraint system for the zk-EVM. gnark (Go) ingests the expanded traces and constraint system, instantiates the circuits and produces the SNARK proof.

    ZK Circuits

    The constraint system lives in the public linea-constraints repo and is authored in a Lisp-style DSL before being compiled to Go. Gnark then turns those constraints into PLONK-compatible circuits over BN254. Internally, Linea’s flow uses a recursive proof stack called Vortex → Arcane → PLONK compression: Vortex/Arcane supply small inner proofs that are finally aggregated into a single PLONK proof that the L1 contract can verify.

    Verification Keys Generation

    Linea uses a Plonk-based proof system which requires a trusted setup. The verification keys are hardcoded in the verifier contract on-chain.

    Validity proofs

    Each update to the system state must be accompanied by a ZK proof that ensures that the new state was derived by correctly applying a series of valid user transactions to the previous state. These proofs are then verified on Ethereum by a smart contract.

    1. LineaRollup.sol - Etherscan source code, finalizeBlocks() and _verifyProof() calls
    2. PlonkVerifierMainnetFull.sol 1 (100% complete)
    3. PlonkVerifierMainnetFull.sol 2 (99% complete)
    Operator

    The system has a centralized sequencer

    Only a trusted sequencer is allowed to submit transaction batches. A mechanism for users to submit their own batches is currently disabled.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    • Funds can be frozen if the sequencer refuses to include an exit transaction (CRITICAL).

    1. LineaRollup.sol - Etherscan source code, onlyRole(OPERATOR_ROLE) modifier

    Users can't force any transaction

    There is no general mechanism to force the sequencer to include the transaction.

    • Users can be censored if the operator refuses to include their transactions.

    Withdrawals

    Regular messaging

    The user initiates L2->L1 messages by submitting a regular transaction on this chain. When the block containing that transaction is settled, the message becomes available for processing on L1. ZK proofs are required to settle blocks. Note that withdrawal requests can be censored by the Sequencer. Currently, there is a general limit of 18750.0 ETH that can be withdrawn within each 1d time window. Users can (eventually, after 6 months of inactivity from the centralized Operator) exit by replacing the Operator. In such a case they need to self-propose and prove their new state on the base layer with the required software which is currently not made available.

    • Funds can be frozen if the operator censors withdrawal transaction.

    1. L1MessageService.sol - Etherscan source code, claimMessageWithProof() function
    2. LineaRollup.sol - Etherscan source code, setFallbackOperator() function
    Permissions
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco

    Ethereum

    Roles:

    Operator (2) 0x46d2…9E3e0x52FF…6754

    Allowed to prove blocks and post the corresponding transaction data.

    Actors:

    CallForwardingProxy 0x3697…367D

    A public proxy contract forwarding calls to a predefined target contract (LineaRollup). Can be called by any address.

    • Can interact with LineaRollup
      • submit and finalize blocks as the Operator role when 6 months of no finalizations have passed
    Linea Multisig 1 0x892b…1DD3
    • A Multisig with 4/8 threshold. It uses the following modules: Roles (The Zodiac ‘Roles’ module for Safe multisigs allows defining roles that can call preconfigured targets on behalf of the Gnosis Safe).
    • Can upgrade with no delay
      • TokenBridge
        via - acting via L1Timelock → ProxyAdmin
      • LineaRollup
        via - acting via L1Timelock → ProxyAdmin
    • Can interact with TokenBridge
      • manage all critical access control roles and permissions (full admin of the main bridge escrow)
    • Can interact with UpgradeableBeacon
      • change the beacon implementation
    • Can interact with LineaRollup
      • manage all critical access control roles and permissions (full admin of the rollup system)
    • Can interact with L1Timelock
      • cancel queued transactions
      • execute transactions that are ready
      • manage all access control roles and change the minimum delay
        via - acting via L1Timelock
      • propose transactions

    Participants (8):

    0x4975…B6aB0x239d…aEFE0x535d…bdF50x5822…40AE0x9376…89920x4CB4…fAD40xab23…55A10xB4dA…dBcb
    Linea Multisig 2 0xB8F5…0051
    • A Multisig with 3/5 threshold.
    • Can interact with L1Timelock
      • propose transactions

    Participants (5):

    0x3acC…B0790x7278…BBD00xF112…E3000xA971…A4510x0645…12F2
    EOA 1 0x453B…bbA8
    • Can interact with Roles
      • pause the TokenBridge, the USDCBridge and the core functionalities of the system (via Roles module, LineaRollup contract)
    Smart contracts
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    TokenBridge 0x051F…3319Implementation (Upgradable)Admin

    Contract used to bridge and escrow ERC-20 tokens.

    • Roles:
      • admin: ProxyAdmin; ultimately Linea Multisig 1
      • defaultAdmin: Linea Multisig 1
    • This contract can store any token.
    Can be upgraded by:
    Linea Multisig 1 with no delay
    BridgedToken 0x36f2…3763

    Standard implementation used for assets that are native to the Linea L2 and bridged back to ethereum.

    PlonkVerifierMainnetFull 0x41A4…bdc7

    Smart contract used to verify the proofs of Linea zkEVM execution.

    UpgradeableBeacon 0x971f…7DeB

    A beacon with an upgradeable implementation currently set as BridgedToken. Beacon proxy contracts pointing to this beacon will all use its implementation.

    • Roles:
      • owner: Linea Multisig 1
    LineaRollup 0xd19d…876FImplementation (Upgradable)Admin

    The main contract of the Linea zkEVM rollup. Contains state roots, the verifier addresses and manages messages between L1 and the L2.

    • Roles:
      • admin: ProxyAdmin; ultimately Linea Multisig 1
      • defaultAdmin: Linea Multisig 1
      • fallbackOperator: CallForwardingProxy
      • operators: EOA 2, EOA 3
    • This contract stores the following tokens: ETH.
    Can be upgraded by:
    Linea Multisig 1 with no delay
    L1Timelock 0xd6B9…0574

    A standard timelock with access control. The current minimum delay is 0s.

    • Roles:
      • canceller: Linea Multisig 1
      • executor: Linea Multisig 1
      • proposer: Linea Multisig 1, Linea Multisig 2
      • timelockAdmin: L1Timelock; ultimately Linea Multisig 1
    PlonkVerifierMainnetFull 0xED39…0995
    Roles 0xF24f…d083

    The Zodiac ‘Roles’ module for Safe multisigs allows defining roles that can call preconfigured targets on behalf of the Gnosis Safe.

    • Roles:
      • pausers: EOA 1
    ProxyAdmin 0xF505…66d6
    • Roles:
      • owner: L1Timelock

    Value Secured is calculated based on these smart contracts and tokens:

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is a 0s delay on code upgrades.