Skip to main content

Security and assurance

This page describes LinethLineth (Formerly the Linea Stack) The open-source ZK-rollup stack, codebase, and technical protocol that's the foundation of Linea Mainnet. Operators can deploy this stack to launch their own Ethereum-compatible L2 or L3 networks. protocol guarantees, operator-controlled security measures, and available assurance evidence.

For trust boundaries and privileged authority, see Trust and responsibilities.

This page does not include:

  • Proof-system maturity statements.
  • Production operations guidance (monitoring, incident response, disaster recovery).
  • Commercial support or SLA commitments.

Protocol-level guarantees​

Under the configured deployment model, Lineth provides:

  • State-transition correctness through zk-SNARKzk-SNARK (Zero-Knowledge Succinct Non-interactive Argument of Knowledge) A type of ZK proof where the prover and verifier don't have to interact. With zk-SNARKs, you can verify 1 transaction or 1 billion transactions in the same amount of time. proof verification on the finalization layerFinalization layer The blockchain where a Lineth deployment submits proofs and state commitments for verification and hard finality. If the finalization layer is Ethereum (an L1), the deployment is an L2. If the finalization layer is Linea (an L2), the deployment is an L3.. A valid proof means the operator cannot finalize an invalid state transition through the normal proof path.
  • Byzantine fault tolerant consensus for deployments that use QBFTQuorum Byzantine Fault Tolerance (QBFT) The Byzantine-fault-tolerant consensus algorithm that Maru implements to let a validator set produce and finalize blocks, tolerating faulty validators in a 3f+1 validator set. with 3f+1 validators. Single-validator deployments do not use QBFT and rely on the operator trust model. See Multi-validator consensus.
  • Settlement finality on the selected finalization layer, scoped to that layer's own finality assumptions. A deployment finalizing to Ethereum inherits Ethereum L1 finality; a deployment finalizing to Linea Mainnet inherits Linea Mainnet's finality, which itself anchors to Ethereum.
  • Bridge and message execution gated by verified state commitments. Messages are tied to verified state transitions in the normal protocol path.

For the trust boundaries behind each of these, see Trust and responsibilities.

Operator-controlled security surfaces​

OperatorsOperator The entity or consortium responsible for deploying, administering, and running the network infrastructure, contracts, keys, access controls, and operational procedures for a network built on Lineth. define and operate their own security boundary. Lineth does not ship a production security operations program. Operators are responsible for:

  • Infrastructure isolation and network security controls
  • Role-based access control (RBAC) for APIs and services.
  • Key management via KMS-backed signing and remote signing through Web3Signer.
  • Governance contracts or multisig controls for privileged roles, proxy administration, and upgrades.
  • Monitoring and incident response tooling.

Governance contracts and multisig controls should be treated as critical security infrastructure. They can hold privileged roles, coordinate emergency response, or control upgrade authority depending on the deployment. Linea Mainnet's Security Council transaction record is one example of how such controls can be documented publicly. For upgrade mechanics, see the OpenZeppelin Transparent Upgradeable Proxy pattern.

Assurance evidence today​

What is published today:

What is not published here:

  • Proof-system maturity statements or current security-review conclusions
  • Per-deployment assurance artifacts

Operators who need assurance evidence for a specific deployment should confirm what is available with the operator of that deployment. Lineth does not generalize one audit or review to all deployments.

Was this page helpful?