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.

No ongoing anomalies detected

Avg. tx data subs. interval

Avg. proof subs. interval

Avg. state updates interval

Past 30 days anomalies

92% normal uptime

Last 30 day anomalies

All liveness anomalies detected for this project in the last 30 days, helping you review recent downtime and availability issues.

No State updates were performed for 2d 8h (from 2026 Sep 02, 03:12 UTC until 2026 Sep 04, 11:15 UTC). These typically occur every 9m 46s on average.

No Tx data submissions were performed for 2d 8h (from 2026 Sep 02, 03:11 UTC until 2026 Sep 04, 11:15 UTC). These typically occur every 20m 44s on average.

Milestones & Incidents

Linea halts for 1 hour

2025 Sep 10th

Learn more

Proof system is complete

2024 Jun 9th

The Linea proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system. and verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. on ethereum covers 100% of the zkEVM.

Learn more

Risk summary

Risk analysis

Sequencer failureState validationData availabilityExit windowProposer failure

Sequencer failure

No mechanism

There is no mechanism to have transactions be included if the sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. is down or censoring. Eventually (after 6 months of no finalized blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over.) the OperatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. role becomes public, theoretically allowing anyone to post data.

State validation

Validity proofs (SN)

SNARKs are succinct zero knowledge proofs that ensure state correctness, but require trusted setupGeneration of a piece of data that must then be used for some cryptographic protocol to run. Generating this data requires some secret information. The "trust" comes from the fact the secret must be destroyed after the ceremony, otherwise cryptographic properties of the protocol could be broken. Once the data is generated, and the secrets are forgotten, no further participation from the creators of the ceremony is required. There are two types of trusted setups for SNARKs: (i) trusted setup per circuit where it is generated from scratch for each circuit, (ii) trusted universal setup per proving system where it can be used for several circuits..

Data availability

Onchain

All of the data needed for proof construction is published on Ethereum L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. 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 upgrade since contracts are instantly upgradable.

Proposer failure

Cannot withdraw

Only the whitelisted proposers can publish state rootsA cryptographic hash succinctly representing a state using a Merkle tree. on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development., so in the event of failure the withdrawals are frozen. Eventually (after 6 months of no finalized blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over.) the OperatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. role becomes public, theoretically allowing anyone to propose state with valid proofs.

Stage

Linea is a

Stage 0

ZK Rollup.

Learn more about Stages

Please keep in mind that these stages do not reflect project security, this is an opinionated assessment of project 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 blobsThe data that a rollup publishes to its L1/data availability (DA) layer. They consist of the L2 transactions that are rolled up, along with some metadata. Blobs are introduced as a new transaction type within Ethereum with EIP-4844, and has rollup scaling specifically in mind. Blobs persist on Ethereum’s Beacon Chain ephemerally. or calldata. This ensures that it will be available for enough time.

Eip4844BlobAcceptor.sol - Etherscan source code, submitBlobs() function

Learn more about the DA layer here:

Ethereum

State derivation

Node software

The nodeA software client that participates in the network. software (Linea Besu) and a guide to reconstruct the state from L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. 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 L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. into batches which are then posted to L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. for proving. Each batch (whether sent as a blobThe data that a rollup publishes to its L1/data availability (DA) layer. They consist of the L2 transactions that are rolled up, along with some metadata. Blobs are introduced as a new transaction type within Ethereum with EIP-4844, and has rollup scaling specifically in mind. Blobs persist on Ethereum’s Beacon Chain ephemerally. 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 proverAn entity that generates the cryptographic proof to convince the verifier that the statement is true. In a ZK-Rollup, the prover generates the ZK (validity) proof to submit to the verifier contract. 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 SNARKShort for "succinct non-interactive argument of knowledge", a SNARK is a widely used type of zero-knowledge proof that is short and fast to verify. Different kinds of SNARKs are usually systematized by proof size, verification time, and type of setup. The most famous SNARKs are Groth16, PLONK/Marlin, Bulletproofs, and STARKs. 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 PLONKA zk-SNARK proving system introduced by Gabizon, Williamson and Ciobotaru in 2019 that allows proving custom circuits. Plonk is based on KZG polynomial commitments and thus requires a universal trusted setup.-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 L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. contract can verify.

Verification Keys Generation

Linea uses a PlonkA zk-SNARK proving system introduced by Gabizon, Williamson and Ciobotaru in 2019 that allows proving custom circuits. Plonk is based on KZG polynomial commitments and thus requires a universal trusted setup.-based proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic proof system. which requires a trusted setupGeneration of a piece of data that must then be used for some cryptographic protocol to run. Generating this data requires some secret information. The "trust" comes from the fact the secret must be destroyed after the ceremony, otherwise cryptographic properties of the protocol could be broken. Once the data is generated, and the secrets are forgotten, no further participation from the creators of the ceremony is required. There are two types of trusted setups for SNARKs: (i) trusted setup per circuit where it is generated from scratch for each circuit, (ii) trusted universal setup per proving system where it can be used for several circuits.. The verification keys are hardcoded in the verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract on-chain.

Validity proofs

PROVER

Linea

Trusted Setups

Onchain verifier

PlonkVerifierFull

Used in

Onchain verifier

PlonkVerifierFull

Used in

Upgrades & Governance

Past upgrades

The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.

Count of upgrades

Last upgrade

29d 1h ago

Avg upgrade interval

6mo 25d

Updates

2026 September 04, 14:03 UTC

High severity

4changes

ETH withdrawal reserve was topped-up, so withdrawal reserve is above minimum again. Also, verifier 0 was upgraded. It is not yet reproduced from the sources.

ETH withdrawal reserve was topped-up, so withdrawal reserve is above minimum again.

Also, verifier 0 was upgraded. It is not yet reproduced from the sources.

-	Status: DELETED
	contract PlonkVerifierFull (eth:0x218C3339ff3fea595c02Ac31Ca8A782f5028C4dc) [N/A]
	+++ description: None

	contract LineaRollup (eth:0xd19d4B5d358258f05D7B411E21A1460D11B0876F) [linea/LineaRollup_ForcedTrx_v8_0] {
	+++ description: 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.
	+++ description: Mapping of proof type to ZK Plonk Verifier contract.
	values.verifiers.0:
-	"eth:0x218C3339ff3fea595c02Ac31Ca8A782f5028C4dc"
+	"eth:0xAFF26999780901ee8B48f0a1271a177ff46fD53F"
	}

	contract YieldManager (eth:0xeb63cABDd78537b9b72A2AFB573F7caa91bd8D94) [linea/YieldManager] {
	+++ description: 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.
	+++ description: True when the LineaRollup ETH balance (the withdrawal reserve backing L2 exits) is below the effective minimum reserve. While true, no more ETH can be moved to the YieldManager or staked, and anyone can permissionlessly trigger unstaking from yield providers (with beacon chain proofs) and replenish the reserve up to the target. Refilling a deficit depends on beacon chain withdrawal latency.
	+++ severity: HIGH
	values.isWithdrawalReserveBelowMinimum:
-	true
+	false
	}

+	Status: CREATED
	contract PlonkVerifierFull (eth:0xAFF26999780901ee8B48f0a1271a177ff46fD53F) [N/A]
	+++ description: None

2026 September 03, 11:32 UTC

High severity

1change

Withdrawal reserve (LineaRollup ETH balance) fell below the 17,500 ETH minimum after a bridge-relayer EOA claimed ~5,087 ETH in three L2- L1 messages on Sep 2, one day after 23,408 ETH was staked into the Lido vault down to the exact 20,000 ETH target. The operator paused staking and requested 5,091 ETH of partial validator withdrawals (EIP-7002) the same hour; the ETH is pending on the beacon chain and will be routed back to the rollup. While the flag is true, no new ETH can be staked and reserve replenishment / unstaking are permissionless.

Withdrawal reserve (LineaRollup ETH balance) fell below the 17,500 ETH minimum after a bridge-relayer EOA claimed ~5,087 ETH in three L2->L1 messages on Sep 2, one day after 23,408 ETH was staked into the Lido vault down to the exact 20,000 ETH target. The operator paused staking and requested 5,091 ETH of partial validator withdrawals (EIP-7002) the same hour; the ETH is pending on the beacon chain and will be routed back to the rollup. While the flag is true, no new ETH can be staked and reserve replenishment / unstaking are permissionless.

	contract YieldManager (eth:0xeb63cABDd78537b9b72A2AFB573F7caa91bd8D94) [linea/YieldManager] {
	+++ description: 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.
	+++ description: True when the LineaRollup ETH balance (the withdrawal reserve backing L2 exits) is below the effective minimum reserve. While true, no more ETH can be moved to the YieldManager or staked, and anyone can permissionlessly trigger unstaking from yield providers (with beacon chain proofs) and replenish the reserve up to the target. Refilling a deficit depends on beacon chain withdrawal latency.
	+++ severity: HIGH
	values.isWithdrawalReserveBelowMinimum:
-	false
+	true
	}

2026 September 01, 12:16 UTC

High severity

8changes

Single line change (replace msg.sender) in the rollup: https://disco.l2beat.com/diff/eth:0x59290394dDC1cF84e671701A929710643c343530/eth:0x052b73d934E9412045Bf731574463Fd026D74645 min and target Reserve percentage ~halved in the yield manager.

Single line change (replace msg.sender) in the rollup: https://disco.l2beat.com/diff/eth:0x59290394dDC1cF84e671701A929710643c343530/eth:0x052b73d934E9412045Bf731574463Fd026D74645

min and target Reserve percentage ~halved in the yield manager.

	contract LineaRollup (eth:0xd19d4B5d358258f05D7B411E21A1460D11B0876F) [linea/LineaRollup_ForcedTrx_v8_0] {
	+++ description: 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.
	sourceHashes.1:
-	"0xf3482110e327210ee9824abef6aa6fea72bf9a49a46187d08853a978c2210c65"
+	"0x99448a403aaba56b396cab263fdccd1a13345cb737178fc7813f1a5bf8d927d5"
	values.$implementation:
-	"eth:0x59290394dDC1cF84e671701A929710643c343530"
+	"eth:0x052b73d934E9412045Bf731574463Fd026D74645"
	values.$pastUpgrades.12:
+	["2026-09-01T09:07:47.000Z","0x0e551aff381b8c6c4c73eafddb326906ac0d3599295444324cee8b988aaa6a6a",["eth:0x052b73d934E9412045Bf731574463Fd026D74645"]]
	values.$upgradeCount:
-	12
+	13
	implementationNames.eth:0x59290394dDC1cF84e671701A929710643c343530:
-	"LineaRollup"
	implementationNames.eth:0x052b73d934E9412045Bf731574463Fd026D74645:
+	"LineaRollup"
	}

	contract YieldManager (eth:0xeb63cABDd78537b9b72A2AFB573F7caa91bd8D94) [linea/YieldManager] {
	+++ description: 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.
	+++ description: Value relative to TVS, part of the computation of minimal rollup ETH reserve.
	values.minimumWithdrawalReservePercentageBps:
-	8500
+	3500
	+++ description: Value relative to TVS, part of the computation of target rollup ETH reserve.
	values.targetWithdrawalReservePercentageBps:
-	9000
+	4000
	}

2026 July 17, 08:50 UTC

High severity

22changes

Upgraded Linea rollup contract to v8.0, diff: https://disco.l2beat.com/diff/eth:0xE68697690E8ff196A6aBB3E1385156D87Df85332/eth:0x59290394dDC1cF84e671701A929710643c343530. The upgrade sets the stage for forced L1 transactions, however they are not live yet. FORCED TRANSACTION SENDER ROLE can send a forced transaction, which defines L2 block number deadline by which the trx must be included, otherwise the rollup operation stops. SET ADDRESS FILTER ROLE can set address filterer, addresses on this list are not allowed to force include trxs on L1 (OFAC compliance is cited). FORCED TRANSACTION SENDER ROLE is not held by anyone yet, preventing from using forced transactions. More precise code changes: - Forced trxs could now be added to the state of the rollup ( nextForcedTransactionNumber , forcedTransactionL2BlockNumbers , forcedTransactionRollingHashes ). - storeForcedTransaction adds a forced trx to the state, it could be called only by FORCED TRANSACTION SENDER ROLE . It doesn't check whether the forced trx fee was paid, whether the blockNumberDeadline is sufficiently in future or whether the sender address is not filtered. Probably these checks will be done in another contract with FORCED TRANSACTION SENDER ROLE permissions. - In finalizeBlocks , several checks are added, including whether all addresses filtered by the sequencer are registered in the filter, whether no forced trx has expired. Also, removed L2Roles Linea ms module on L2. Also, upgraded Linea verifier, not reproduced yet.

Upgraded Linea rollup contract to v8.0, diff: https://disco.l2beat.com/diff/eth:0xE68697690E8ff196A6aBB3E1385156D87Df85332/eth:0x59290394dDC1cF84e671701A929710643c343530.

The upgrade sets the stage for forced L1 transactions, however they are not live yet. FORCED_TRANSACTION_SENDER_ROLE can send a forced transaction, which defines L2 block number deadline by which the trx must be included, otherwise the rollup operation stops. SET_ADDRESS_FILTER_ROLE can set address filterer, addresses on this list are not allowed to force include trxs on L1 (OFAC compliance is cited). FORCED_TRANSACTION_SENDER_ROLE is not held by anyone yet, preventing from using forced transactions.

More precise code changes:

Forced trxs could now be added to the state of the rollup (nextForcedTransactionNumber, forcedTransactionL2BlockNumbers, forcedTransactionRollingHashes).
storeForcedTransaction adds a forced trx to the state, it could be called only by FORCED_TRANSACTION_SENDER_ROLE. It doesn’t check whether the forced trx fee was paid, whether the _blockNumberDeadline is sufficiently in future or whether the sender address is not filtered. Probably these checks will be done in another contract with FORCED_TRANSACTION_SENDER_ROLE permissions.
In _finalizeBlocks, several checks are added, including whether all addresses filtered by the sequencer are registered in the filter, whether no forced trx has expired.

Also, removed L2Roles Linea ms module on L2.

Also, upgraded Linea verifier, not reproduced yet.

-	Status: DELETED
	contract PlonkVerifierFull (eth:0x0D0f070386edC441A63fB8FAe8FB937Bbd88c5Cb) [N/A]
	+++ description: None

	contract LineaRollup (eth:0xd19d4B5d358258f05D7B411E21A1460D11B0876F) [linea/LineaRollup_ForcedTrx_v8_0] {
	+++ description: 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.
	template:
-	"linea/LineaRollup_NativeYield_v7_1"
+	"linea/LineaRollup_ForcedTrx_v8_0"
	sourceHashes.1:
-	"0x61e0da7291b49dc345bdfe09390ff5f67c0d1ad182602ba2b4c238eb023dda50"
+	"0xf3482110e327210ee9824abef6aa6fea72bf9a49a46187d08853a978c2210c65"
	values.$implementation:
-	"eth:0xE68697690E8ff196A6aBB3E1385156D87Df85332"
+	"eth:0x59290394dDC1cF84e671701A929710643c343530"
	values.$pastUpgrades.11:
+	["2026-07-16T11:32:59.000Z","0x4bcfe7ea1724555288f7cf4d7a0de608182483a41d670e3027b89c3e989240c9",["eth:0x59290394dDC1cF84e671701A929710643c343530"]]
	values.$upgradeCount:
-	11
+	12
	values.CONTRACT_VERSION:
-	"7.1"
+	"8.0"
	+++ description: Mapping of proof type to ZK Plonk Verifier contract.
	values.verifiers.1:
-	"eth:0x0D0f070386edC441A63fB8FAe8FB937Bbd88c5Cb"
+	"eth:0x09ac9f7E5Fb37e241e0B1e52aaF01eFE0a488a77"
	values.addressFilter:
+	"eth:0x526AE78F0103Ae73F05449ae30eb626C1003784E"
	values.FORCED_TRANSACTION_FEE_SETTER_ROLE:
+	"0xdaafd36d8da81d5104d4fd21e3ccc58683c62ba08cd23875bcfbc0583a3f49dd"
	values.FORCED_TRANSACTION_SENDER_ROLE:
+	"0xb63b70db607c764adad98a6745fc4efcea212ebc7b501d5753c57d675f377a66"
	values.forcedTransactionFeeInWei:
+	1000000000000000
	values.getRequiredForcedTransactionFields:
+	{"finalizedState":"0x6af94bc910a5facbc347462f6b2bc840940b7c99ae3cb483742dfd2c74c9d60f","previousForcedTransactionRollingHash":"0x0000000000000000000000000000000000000000000000000000000000000000","previousForcedTransactionBlockDeadline":0,"currentFinalizedL2BlockNumber":31407522,"forcedTransactionFeeAmount":1000000000000000}
	values.SET_ADDRESS_FILTER_ROLE:
+	"0x012c76ef7f96cd7eb95acbdc250ad5696bbe3fd2fcf0207571939fa40c2e0167"
	implementationNames.eth:0xE68697690E8ff196A6aBB3E1385156D87Df85332:
-	"LineaRollup"
	implementationNames.eth:0x59290394dDC1cF84e671701A929710643c343530:
+	"LineaRollup"
	}

	contract YieldManager (eth:0xeb63cABDd78537b9b72A2AFB573F7caa91bd8D94) [linea/YieldManager] {
	+++ description: 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.
	+++ description: Value relative to TVS, part of the computation of minimal rollup ETH reserve.
	values.minimumWithdrawalReservePercentageBps:
-	9000
+	8500
	+++ description: Value relative to TVS, part of the computation of target rollup ETH reserve.
	values.targetWithdrawalReservePercentageBps:
-	9888
+	9000
	}

-	Status: DELETED
	contract L2Roles (linea:0x3886a948eA7b4053312c3aE31a13776144aA6239) [linea/L2Roles]
	+++ description: The Zodiac 'Roles' module for Safe multisigs allows defining roles that can call preconfigured targets on behalf of the Gnosis Safe.

	contract Linea Multisig 3 (linea:0xf5cc7604a5ef3565b4D2050D65729A06B68AA0bD) [GnosisSafe] {
	+++ description: None
	values.GnosisSafe_modules.0:
-	"linea:0x3886a948eA7b4053312c3aE31a13776144aA6239"
	}

+	Status: CREATED
	contract PlonkVerifierFull (eth:0x09ac9f7E5Fb37e241e0B1e52aaF01eFE0a488a77) [N/A]
	+++ description: None

+	Status: CREATED
	contract AddressFilter (eth:0x526AE78F0103Ae73F05449ae30eb626C1003784E) [linea/AddressFilter]
	+++ description: None

2026 May 04, 10:44 UTC

High severity

17changes

Upgraded Linea SC to Safe v1.4.1: https://github.com/safe-fndn/safe-smart-account/blob/release/v1.4.1/contracts/Safe.sol, upgraded Linea Multisig 3 to SafeL2 v1.4.1: https://github.com/safe-fndn/safe-smart-account/blob/release/v1.4.1/contracts/SafeL2.sol. Adjusted targetWithdrawalReservePercentageBps yield parameter, reduced the total amount of ether that can leave L2MessageService on Linea L2 per day.

Adjusted targetWithdrawalReservePercentageBps yield parameter, reduced the total amount of ether that can leave L2MessageService on Linea L2 per day.

	contract Linea Security Council (eth:0x892bb7EeD71efB060ab90140e7825d8127991DD3) {
	+++ description: None
	sourceHashes.1:
-	"0xd42bbf9f7dcd3720a7fc6bdc6edfdfae8800a37d6dd4decfa0ef6ca4a2e88940"
+	"0x7d388119a66f3eae147d748f86136f073d907d6b36f7e87e9363c4c7a2899a8a"
	values.$implementation:
-	"eth:0xd9Db270c1B5E3Bd161E8c8503c55cEABeE709552"
+	"eth:0x41675C099F32341bf84BFc5382aF534df5C7461a"
	values.$members.1:
-	"eth:0x497515578b0BE54d2f0f32cF3F08B85Bf8cEB6aB"
+	"eth:0xD6481cC92eD746EbC679788654723Ce49D45EbeA"
	values.$members.7:
-	"eth:0x99234cd9B532F30538ac797D33c212e3B69Fd087"
+	"eth:0x0F4df4939a6B126a088A40B4Bbf9F30337ACBFE4"
	values.VERSION:
-	"1.3.0"
+	"1.4.1"
	implementationNames.eth:0xd9Db270c1B5E3Bd161E8c8503c55cEABeE709552:
-	"GnosisSafe"
	implementationNames.eth:0x41675C099F32341bf84BFc5382aF534df5C7461a:
+	"Safe"
	}

	contract YieldManager (eth:0xeb63cABDd78537b9b72A2AFB573F7caa91bd8D94) {
	+++ description: 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.
	+++ description: Value relative to TVS, part of the computation of target rollup ETH reserve.
	values.targetWithdrawalReservePercentageBps:
-	9980
+	9888
	}

	contract L2MessageService (linea:0x508Ca82Df566dCD1B0DE8296e70a96332cD644ec) {
	+++ description: None
	+++ description: The cap on the total amount of ether that can leave the contract via L1 -> L2 message claims per period given by periodInSeconds.
	values.limitInWei:
-	"24000000000000000000000"
+	"8000000000000000000000"
	}

	contract Linea Multisig 3 (linea:0xf5cc7604a5ef3565b4D2050D65729A06B68AA0bD) {
	+++ description: None
	sourceHashes.1:
-	"0x59fe14e95a8aa7f52213f18bae5c9329cf583a7ba31194698b15eddb97d5e825"
+	"0x618c83d2fbbe19fd6f2d6ee6ee79a60e6206e48bf361eaf4812e1c1fc14b4527"
	values.$implementation:
-	"linea:0x3E5c63644E683549055b9Be8653de26E0B4CD36E"
+	"linea:0x29fcB43b46531BcA003ddC8FCB67FFE91900C762"
	values.$members.2:
-	"linea:0x497515578b0BE54d2f0f32cF3F08B85Bf8cEB6aB"
+	"linea:0xD6481cC92eD746EbC679788654723Ce49D45EbeA"
	values.$members.8:
-	"linea:0x99234cd9B532F30538ac797D33c212e3B69Fd087"
+	"linea:0x0F4df4939a6B126a088A40B4Bbf9F30337ACBFE4"
	values.VERSION:
-	"1.3.0"
+	"1.4.1"
	implementationNames.linea:0x3E5c63644E683549055b9Be8653de26E0B4CD36E:
-	"GnosisSafeL2"
	implementationNames.linea:0x29fcB43b46531BcA003ddC8FCB67FFE91900C762:
+	"SafeL2"
	}

+	Status: CREATED
	contract Safe (eth:0xD6481cC92eD746EbC679788654723Ce49D45EbeA)
	+++ description: None

Operator

The system has a centralized sequencer

Only a trusted sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. 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).

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

Users can't force any transaction

There is no general mechanism to force the sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. to include the transaction.

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

Withdrawals

Regular messaging

The user initiates L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups.->L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. messages by submitting a regular transaction on this chain. When the blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. 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 SequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs.. Currently, there is a general limit of 10000.0 ETH that can be withdrawn within each 1d time window. Users can (eventually, after 6 months of inactivity from the centralized OperatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades.) 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.

Permissions

A dashboard to explore contracts and permissions

Go to Disco

Explore in Disco

Ethereum

Actors:

CallForwardingProxy0x3697…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 blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. as the OperatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. role when 6 months of no finalizations have passed

Linea Security Council0x892b…1DD3

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 bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a 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 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
- manage all critical access control roles and permissions (full admin of the rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. system)
- pause the rollup for 2d, followed by 2d cooldown, during which the rollup cannot be paused, except by the Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.
- pause the rollup indefinitely
- send ETH from the rollup bridge to the YieldManager
- set the address of the yield manager contract that receives ETH from rollup bridge
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

Participants (9):

0x1f0c…3c4f Safe 0xD303…Ae8d 0x535d…bdF5 0xC263…bc82 0x9376…8992 0x4CB4…fAD4 0x0F4d…BFE4 0xB4dA…dBcb

Linea Multisig 20xB8F5…0051

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

Participants (5):

0x3acC…B079 0x7278…BBD0 0x7E55…68c5 0xA971…A451 0x0645…12F2

Safe0xD648…EbeA

A Multisig with 1/4 threshold. Member of Linea Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups..

Participants (4):

0xBEA0…2c77 0xaa8f…4CF2 0xd7dE…a1eA 0xb6Ff…140b

EOA 10x2532…42d0

Can interact with TokenBridge
- can pause the bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge.
Can interact with LineaRollup
- pause the rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. for 2d, followed by 2d cooldown, during which the rollup cannot be paused, except by the Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.

2 EOAs

EOA 2 EOA 3

Can interact with LineaRollup
- Allowed to prove blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. and post the corresponding transaction data

EOA 40x89F1…388c

Can interact with AddressFilter
- add and remove addresses to the filter list. Addresses in this list can not send forced transactions from L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.

EOA 50xcEE1…d448

Can interact with LineaRollup
- send ETH from the rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. to the YieldManager
Can interact with YieldManager
- operate native yield staking: stake and unstake, collect yield, pause and unpause, ossify yield managers

Linea

Actors:

Linea Multisig 40xB8F5…0051

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

Participants (5):

0x3acC…B079 0x7278…BBD0 0x7E55…68c5 0xA971…A451 0x0645…12F2

Linea Multisig 30xf5cc…A0bD

A Multisig with 5/9 threshold.

Can upgrade with no delay
- TokenBridge L2Timelock → ProxyAdmin
- L2MessageService L2Timelock → ProxyAdmin
- L2USDCBridge ProxyAdmin
Can interact with TokenBridge
- can pause the bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a 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 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

Participants (9):

0x1f0c…3c4f 0xD303…Ae8d 0xD648…EbeA 0x4CB4…fAD4 0xB4dA…dBcb 0x9376…8992 0x535d…bdF5 0xC263…bc82 0x0F4d…BFE4

EOA 60x2532…42d0

Can interact with TokenBridge
- can pause the bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge.

EOA 70x2b0F…7652

Can interact with L2MessageService
- Can anchor L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. data on the L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups.. A check is supposed to be added to the proof systemThe infrastructure that allows projects to verify their state transitions. It is composed by onchain verifiers and offchain provers. The main two flavors are optimistic and ZK proof systems, but they can be combined in a hybrid model. In general though, if a system is able to accept state roots optimistically, even if it has a ZK component, it is considered an optimistic 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 livenessLiveness refers to the ability of a system to respond to requests and to process them in a timely manner. In the context of L2s, it refers to the ability of settling transactions, proofs and state roots to the base layer. failure by posting an invalid anchor

Smart contracts

A dashboard to explore contracts and permissions

Go to Disco

Explore in Disco

A diagram of the smart contract architecture

Ethereum

TokenBridge

Escrow

0x051F…3319 Implementation (Upgradable)Admin

Contract used to bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. and escrow ERC-20 tokens.

Roles:
- admin: ProxyAdmin; ultimately Linea Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.
- allPausers: EOA 1, Linea Security Council
- allUnpausers: Linea Security Council
- completeTokenBridgingPausers: Linea Security Council
- completeTokenBridgingUnpausers: Linea Security Council
- customContractSetters: Linea Multisig 2, Linea Security Council; ultimately Linea Security Council
- defaultAdmin: Linea Security Council
- initiateTokenBridgingPausers: Linea Security Council
- initiateTokenBridgingUnpausers: Linea Security Council
- messageServiceSetters: Linea Security Council
- reserveTokenRemovers: Linea Multisig 2, Linea Security Council; ultimately Linea Security Council
- reserveTokenSetters: Linea Multisig 2, Linea Security Council; ultimately Linea Security Council

All supported tokens in this escrow are included in the value secured calculation.

Can be upgraded by:

Linea Security Council with no delay

PlonkVerifierFull

2 instances

0x09ac…8a77 0xAFF2…D53F

BridgedToken0x36f2…3763

Standard implementation used for assets that are native to the other layer and are bridged to this layer.

ProxyAdmin0x41fA…6eb5

Roles:
- owner: Linea Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.

LidoStVaultYieldProvider0x486D…EEC3

Yield provider adaptor, delegatecalled by the YieldManager, that deploys rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. ETH into a Lido V3 staking vault (stVault) and its beacon chain validatorsIn the context of L2s, a Validator is an actor that validates the correctness of state transitions. For optimistic rollups this corresponds to challengers, and for ZK rollups this corresponds to the onchain verifier. Withdrawals back to the reserve are requested via EIP-7002 partial validator withdrawals, so refilling the reserve is subject to beacon chain latency; while the reserve is in deficit anyone can trigger them with a validator proof.

L1USDCBridge0x504A…88ce Implementation (Upgradable)Admin

L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. side of the old and now unused USDC bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge..

Roles:
- admin: ProxyAdmin; ultimately Linea Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.

Can be upgraded by:

Linea Security Council with no delay

AddressFilter0x526A…784E

Blocklist consulted by the LineaRollup forced-transaction path: an address on this list cannot force-include transactions from L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development., so the contract gates the escape hatchThe facility for any user of a rollup to exit the system with their assets under any circumstance. Most relevant in rollups with a centralized proposer, wherein users do not have the ability to propose blocks, but can nonetheless exit the rollup by interacting with a smart contract on L1..

Roles:
- defaultAdmin: EOA 4

Delay0x784C…5436

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 Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.
- zodiacModule_modules: Linea Security Council

UpgradeableBeacon0x971f…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 Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.

LineaRollup

Escrow

0xd19d…876F Implementation (Upgradable)Admin

The main contract of the Linea zkEVM rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup.. Contains state rootsA cryptographic hash succinctly representing a state using a Merkle tree., the verifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. addresses and manages messages between L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development. and the L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups.. ETH deployed to the rollup contract can be transfered to a yield protocol.

Roles:
- admin: ProxyAdmin; ultimately Linea Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.
- defaultAdmin: Linea Security Council
- ethStaker: EOA 5, Linea Security Council
- livenessRecoveryOperator: CallForwardingProxy
- operators: EOA 2, EOA 3
- pauseAll: EOA 1, Linea Security Council
- securityCouncil: Linea Security Council
- yieldManagerSetter: Linea Security Council

The following tokens are included in the value secured calculation:

Can be upgraded by:

Linea Security Council with no delay

Timelock0xd6B9…0574

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

Roles:
- canceller: Linea Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.
- executor: Linea Security Council
- proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block.: Linea Multisig 2, Linea Security Council; ultimately Linea Security Council
- timelockAdmin: Timelock; ultimately Linea Security Council

YieldManager0xeb63…8D94 Implementation (Upgradable)Admin

Manages flows of ETH and staked ETH in and out of rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. contract reserves. Tracks the available ETH balance for L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. exits, configures target parameters for amount of staked ETH, communicates with yield provider adaptors.

Roles:
- admin: ProxyAdmin; ultimately Linea Security CouncilA Security Council is a sufficiently decentralized set of members that is able to upgrade a system. A properly set up Security Council consists of at least 8 members with a threshold greater than 75%. What 'sufficiently decentralized' means is fundamentally subjective and L2BEAT evaluates each case individually. A Security Council is allowed to instantly upgrade Stage 1 rollups.
- yieldStakingManager: Linea Security Council
- yieldStakingOperator: EOA 5, Linea Security Council

Can be upgraded by:

Linea Security Council with no delay

ProxyAdmin0xF505…66d6

Roles:
- owner: Timelock

Linea

ProxyAdmin0x1E1f…774E

Roles:
- owner: L2Timelock

TokenBridge0x3530…ceB9 Implementation (Upgradable)Admin

Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 3
- allPausers: EOA 6, 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
- reserveTokenRemovers: Linea Multisig 3, Linea Multisig 4
- reserveTokenSetters: Linea Multisig 3, Linea Multisig 4

Can be upgraded by:

Linea Multisig 3 with no delay

L2MessageService0x508C…44ec Implementation (Upgradable)Admin

Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 3
- l1l2MessageSetter: EOA 7

Can be upgraded by:

Linea Multisig 3 with no delay

L2USDCBridge0xA2Ee…504A Implementation (Upgradable)Admin

L2Layer 2 (L2) is a category of technical solutions aimed to scale the base layer in a trust minimized way. This category includes solutions like rollups as well as state channels and plasma. Other solutions are able to scale further, but with the introduction of additional trust assumptions, which are therefore not trust minimized. Sometimes the term Layer 2 is used to refer to include these solutions too, like validiums and optimiums, but to distinguish between trust minimized and non trust minimized solutions they are often referred to as "light" L2s, opposed to "strong" L2s like rollups. side of the old and now unused USDC bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge..

Roles:
- admin: ProxyAdmin; ultimately Linea Multisig 3

Can be upgraded by:

Linea Multisig 3 with no delay

L2Timelock0xc808…56ca

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

Roles:
- canceller: Linea Multisig 3
- executor: Linea Multisig 3
- proposerIn the context of L2s, the actor that proposes a claimed state root on L1. The term is also used in the context of Ethereum to refer to the actor that proposes a new block.: Linea Multisig 3, Linea Multisig 4
- timelockAdmin: L2Timelock; ultimately Linea Multisig 3

ProxyAdmin0xcB04…A30c

Roles:
- owner: Linea Multisig 3

LineaVoyageXP0xd83a…599A

Voyage XP tokens are non-transferrable, soulbound tokens that are distributed to recognize the community’s contribution toward the growth of the Linea ecosystem.

BridgedToken0xda8A…49dF

Standard implementation used for assets that are native to the other layer and are bridged to this layer.

UpgradeableBeacon0xE798…02c0

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