Search
Search for projects by name or address
Linea
Badges
About
Linea is a ZK Rollup powered by a zkEVM developed at Consensys, designed to scale the Ethereum network.
Badges
About
Linea is a ZK Rollup powered by a zkEVM developed at Consensys, designed to scale the Ethereum network.
2025 Mar 12 — 2026 Mar 12
The section shows the operating costs that L2s pay to Ethereum.
2025 Mar 13 — 2026 Mar 12
This section shows how much data the project publishes to its data-availability (DA) layer over time. The project currently posts data to
Ethereum.
2025 Mar 13 — 2026 Mar 12
This section shows how "live" the project's operators are by displaying how frequently they submit transactions of the selected type. It also highlights anomalies - significant deviations from their typical schedule.
Proof system is complete
2024 Jun 9th
The Linea proof system and verifier on ethereum covers 100% of the zkEVM.
Funds can be stolen if
Funds can be frozen if
Users can be censored if
MEV can be extracted if
SNARKs are succinct zero knowledge proofs that ensure state correctness, but require trusted setup.
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.
There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
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.
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.
EthereumThe 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.
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.
Is available via the official Linea docs for Linea Besu (preloaded), Besu, Erigon, Nethermind, Geth.
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.
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.
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.
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.
Linea uses a Plonk-based proof system which requires a trusted setup. The verification keys are hardcoded in the verifier contract on-chain.
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.
Trusted Setups
Used in
Verifiers
Used in | Verifiers 2by |
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).
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.
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 30000.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.
Ethereum
Actors:
A Multisig with 5/9 threshold.
- Can upgrade with no delay
- TokenBridge Timelock → ProxyAdmin
- L1USDCBridge ProxyAdmin
- LineaRollup Timelock → ProxyAdmin
- YieldManager Timelock → ProxyAdmin
- Can interact with TokenBridge
- can pause the bridge
- can pause token bridging actions initiated from the other layer
- can pause token bridging actions initiated from this layer
- can prevent tokens that have not been bridged already from being bridged by assigning them a reserved status with 3mo delay or with no delay Delay with 3mo delay → Linea Multisig 2 - or - acting directly
- can remove the reserved status from a token, meaning that it is allowed to be bridged again with 3mo delay or with no delay Delay with 3mo delay → Linea Multisig 2 - or - acting directly
- can set custom ERC20 contracts for specific ERC20s with 3mo delay or with no delay Delay with 3mo delay → Linea Multisig 2 - or - acting directly
- can set the contract that is recognized to be the token bridge contract on the other side
- can set the contract used as the source of truth from crosschain messages
- can unpause token bridging actions initiated from the other layer
- can unpause token bridging actions initiated from this layer
- manage all critical access control roles and permissions (full admin of the main bridge escrow)
- Can interact with Delay
- enable/disable the module, set delays and expiration of transactions, set the target with 3mo delay Delay with 3mo delay → Linea Multisig 2
- Can interact with UpgradeableBeacon
- change the beacon implementation
- Can interact with LineaRollup
- Can interact with Timelock
- cancel queued transactions
- execute transactions that are ready
- manage all access control roles and change the minimum delay Timelock
- propose transactions with 3mo delay or with no delay Delay with 3mo delay → Linea Multisig 2 - or - acting directly
- Can interact with YieldManager
- manage native yield staking: modify reserve parameters, set yield pools, set yield receiver addresses
- operate native yield staking: stake and unstake, collect yield, pause and unpause, ossify yield managers
A Multisig with 3/5 threshold. It uses the following modules: Delay (A simple Safe module for that can queue and execute transactions as Linea Multisig 2 after a delay of currently 3mo, if registered as a module there).
- Can interact with TokenBridge
- can prevent tokens that have not been bridged already from being bridged by assigning them a reserved status
- can remove the reserved status from a token, meaning that it is allowed to be bridged again
- can set custom ERC20 contracts for specific ERC20s
- Can interact with Delay
- enable/disable the module, set delays and expiration of transactions, set the target
- Can interact with Timelock
- propose transactions
- An Operator - acting directly
Linea
Actors:
A Multisig with 3/5 threshold.
- Can interact with TokenBridge
- can prevent tokens that have not been bridged already from being bridged by assigning them a reserved status
- can remove the reserved status from a token, meaning that it is allowed to be bridged again
- can set custom ERC20 contracts for specific ERC20s
- Can interact with L2Timelock
- propose transactions
A Multisig with 5/9 threshold. It uses the following modules: L2Roles (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 L2Timelock → ProxyAdmin
- L2MessageService L2Timelock → ProxyAdmin
- L2USDCBridge ProxyAdmin
- Can interact with TokenBridge
- can pause the bridge
- can pause token bridging actions initiated from the other layer
- can pause token bridging actions initiated from this layer
- can prevent tokens that have not been bridged already from being bridged by assigning them a reserved status
- can remove the reserved status from a token, meaning that it is allowed to be bridged again
- can set custom ERC20 contracts for specific ERC20s
- can set the contract that is recognized to be the token bridge contract on the other side
- can set the contract used as the source of truth from crosschain messages
- can unpause token bridging actions initiated from the other layer
- can unpause token bridging actions initiated from this layer
- manage all critical access control roles and permissions (full admin of the main bridge escrow)
- Can interact with L2Timelock
- cancel queued transactions
- execute transactions that are ready
- manage all access control roles and change the minimum delay L2Timelock
- propose transactions
- Can interact with UpgradeableBeacon
- change the beacon implementation
- Can interact with L2MessageService
- Can anchor L1 data on the L2. A check is supposed to be added to the proof system on L1 so that it is not possible to settle if the anchor is not correct. The function is permissioned because otherwise anyone can cause a liveness failure by posting an invalid anchor
- Can interact with L2Roles
- can pause the L2MessageService, the TokenBridge and the L2USDCBridge
- Can interact with L2Roles
- can mint XP soulbound tokens as part of the Voyage campaign
Ethereum
Contract used to bridge and escrow ERC-20 tokens.
- Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 1
- allPausers: Linea Multisig 1
- allUnpausers: Linea Multisig 1
- completeTokenBridgingPausers: Linea Multisig 1
- completeTokenBridgingUnpausers: Linea Multisig 1
- customContractSetters: Linea Multisig 1, Linea Multisig 2; ultimately Linea Multisig 1
- defaultAdmin: Linea Multisig 1
- initiateTokenBridgingPausers: Linea Multisig 1
- initiateTokenBridgingUnpausers: Linea Multisig 1
- messageServiceSetters: Linea Multisig 1
- remoteTokenBridgeSetters: Linea Multisig 1
- reserveTokenRemovers: Linea Multisig 1, Linea Multisig 2; ultimately Linea Multisig 1
- reserveTokenSetters: Linea Multisig 1, Linea Multisig 2; ultimately Linea Multisig 1
All supported tokens in this escrow are included in the value secured calculation.
Standard implementation used for assets that are native to the other layer and are bridged to this layer.
- Roles:
- owner: Linea Multisig 1
A simple Safe module for that can queue and execute transactions as Linea Multisig 2 after a delay of currently 3mo, if registered as a module there.
- Roles:
- owner: Linea Multisig 2; ultimately Linea Multisig 1
- zodiacModule_modules: Linea Multisig 1
Smart contract used to verify the proofs of Linea zkEVM execution.
Smart contract used to verify the proofs of Linea zkEVM execution.
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
The main contract of the Linea zkEVM rollup. Contains state roots, the verifier addresses and manages messages between L1 and the L2. ETH deployed to the rollup contract can be transfered to a yield protocol.
- Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 1
- defaultAdmin: Linea Multisig 1
- ethStaker: EOA 3, Linea Multisig 1
- fallbackOperator: CallForwardingProxy
- operators: EOA 1, EOA 2
- yieldManagerSetter: Linea Multisig 1
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; ultimately Linea Multisig 1
- timelockAdmin: Timelock; ultimately Linea Multisig 1
Manages flows of ETH and staked ETH in and out of rollup contract reserves. Tracks the available ETH balance for L2 exits, configures target parameters for amount of staked ETH, communicates with yield provider adaptors.
- Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 1
- yieldStakingManager: Linea Multisig 1
- yieldStakingOperator: EOA 3, Linea Multisig 1
- Roles:
- owner: Timelock
Linea
- Roles:
- owner: L2Timelock
Contract used to bridge and escrow ERC-20 tokens.
- Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 3
- allPausers: Linea Multisig 3
- allUnpausers: Linea Multisig 3
- completeTokenBridgingPausers: Linea Multisig 3
- completeTokenBridgingUnpausers: Linea Multisig 3
- customContractSetters: Linea Multisig 3, Linea Multisig 4
- defaultAdmin: Linea Multisig 3
- initiateTokenBridgingPausers: Linea Multisig 3
- initiateTokenBridgingUnpausers: Linea Multisig 3
- messageServiceSetters: Linea Multisig 3
- remoteTokenBridgeSetters: Linea Multisig 3
- reserveTokenRemovers: Linea Multisig 3, Linea Multisig 4
- reserveTokenSetters: Linea Multisig 3, Linea Multisig 4
The Zodiac ‘Roles’ module for Safe multisigs allows defining roles that can call preconfigured targets on behalf of the Gnosis Safe.
- Roles:
- pausers: EOA 5
- voyageXpMinters: EOA 6
- Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 3
- l1l2MessageSetter: EOA 4
A standard timelock with access control. The current minimum delay is 0s.
- Roles:
- canceller: Linea Multisig 3
- executor: Linea Multisig 3
- proposer: Linea Multisig 3, Linea Multisig 4
- timelockAdmin: L2Timelock; ultimately Linea Multisig 3
- Roles:
- owner: Linea Multisig 3
Voyage XP tokens are non-transferrable, soulbound tokens that are distributed to recognize the community’s contribution toward the growth of the Linea ecosystem.
Standard implementation used for assets that are native to the other layer and are bridged to this layer.
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 3
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.