Compliance

This page describes how to use a 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. deployment's protocol evidence in your own compliance program. 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. design the program and map its controls to their own obligations. Lineth does not certify a deployment against a regulatory framework.

For protocol guarantees, operator-controlled surfaces, cryptographic primitives, and assurance evidence, see Security and assurance.

Deployment evidence

A Lineth deployment produces evidence you can cite in your compliance program:

• State commitments posted to 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.
• 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 records on the finalization layer
• Finalization records on the finalization layer
• Transaction history retained by the deployment's data availability model

What participants can reconstruct or verify from that evidence depends on the deployment model. See Trust model for trust and verification boundaries.

Retention and disclosure

Operators implement retention and disclosure against their own policy, using the deployment's data availability and access control configuration. They connect their own compliance, monitoring, and logging systems to the deployment.

See also

• Security and assurance: Protocol guarantees and published assurance evidence.
• Trust model: What each component can do, and what participants can verify.