> For the complete Linea documentation index, see [llms.txt](/llms.txt). > Agents can fetch this page as Markdown at [https://docs.linea.build/stack.md](https://docs.linea.build/stack.md). # Lineth Stack Lineth (formerly the Linea Stack) is the collection of protocol components, onchain contracts, and operational capabilities that you can use to deploy your own Layer 2 or Layer 3 network, inheriting a [ZK proof](/protocol/reference/zero-knowledge-glossary#zero-knowledge-proof)**Zero-knowledge proof** A cryptographic method that allows an individual to prove that a statement is true without conveying any additional information. This is useful for scaling blockchain networks through rollups, because it reduces the amount of information you have to provide to lower layers. system and Ethereum-compatible execution. [Lineth is distinct from Linea](/protocol/linea-vs-lineth), the public network built on Lineth. Use this documentation to evaluate and design a custom Lineth deployment. Get started: [ Evaluate Lineth Assess deployment models, trust assumptions, privacy, security, and compliance. This section helps determine whether Lineth is a suitable foundation for your use case. ](/stack/evaluate)[ Design a deployment architecture Explore the components and design choices in a Lineth deployment, including data availability, finality, and access control. This section provides a reference architecture. ](/stack/deployment)[ Run a local deployment Start a Lineth stack, deploy contracts, produce L2 blocks, and verify finalization against a local L1 or Sepolia. This quickstart is an evaluation environment only. ](/stack/how-to/run-local-lineth-stack)[ Prepare for production A production deployment requires environment-specific guidance that is outside the scope of these docs. Contact support to review your deployment model, production architecture, implementation plan, configuration, and operating model. ](/support) tip For protocol mechanics beneath the operator stack, see [Protocol](/protocol). For the public network overview, see [Linea Mainnet](/network). ## Why Lineth? Organizations that need capabilities beyond those of a public [L1](/protocol/reference/zero-knowledge-glossary#layer-1-l1)**Layer 1 (L1)** The underlying foundation and base blockchain that various L2 networks build on top of. For example, Ethereum is an L1 that is comprised of node operators to secure and validate the network, block producers, the history of transaction data, and the consensus mechanism of the blockchain itself. or [L2](/protocol/reference/zero-knowledge-glossary#layer-2-l2)**Layer 2 (L2)** A separate blockchain that increases transaction speed and throughput, while deriving its security from Ethereum. L2s rely on Ethereum for data availability by posting their transaction data onto Ethereum. face "the institutional blockchain trilemma," a three-way trade-off between the following: - **Privacy and control:** Permissionless networks do not provide the configurable access, compliance, governance, and data visibility controls many institutions require. - **Interoperability and liquidity:** Standalone networks risk becoming silos. Institutions need to transact with each other and connect to liquidity and applications across public ecosystems, not just within a single chain. - **Predictable performance, security, and cost:** Activity on shared public networks can affect capacity and fees. An independent L1 offers isolation, but requires operators to fund and maintain their own consensus and security model. The institutional blockchain trilemma: privacy and control, interoperability and liquidity, and performance, security, and cost. Privacy andcontrolInteroperabilityand liquidityPerformance, security,and costPermissionless networks lackconfigurable access, compliance,governance, and data visibility.Standalone networks become silos,without a path to public liquidityand applications.A custom L1 isolates capacity andfees, but operators fund a separateconsensus and security model. The institutional blockchain trilemma: privacy and control, interoperability and liquidity, and performance, security, and cost. Privacy andcontrolInteroperabilityand liquidityPerformance, security,and cost Lineth is the open-source stack for institutions to run their own Ethereum-equivalent network. By combining configurable privacy and control, connectivity across institutional and public networks, and dedicated execution with more predictable costs, Lineth allows institutions to optimize their position in this trilemma. For example, a Lineth [private validium](/protocol/reference/zero-knowledge-glossary#validium)**Validium** A deployment model in which a Lineth network proves state transitions with zk-SNARKs but keeps transaction data in a private data availability layer instead of publishing it to the finalization layer. Only state commitments and proofs are posted onchain, so participants without access to the offchain data can't independently reconstruct or verify the full transaction history. inherits the security of a public network while keeping private data off that network and avoiding the cost and complexity of maintaining a separate consensus layer. ## Key features A custom Lineth network has the same protocol foundations as [Linea Mainnet](/network). [Operators](/protocol/reference/zero-knowledge-glossary#operator)**Operator** 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. configure access, data availability, and finalization to match their requirements. At a high level, Lineth provides: - **Ethereum-compatible execution:** Run an Ethereum-equivalent network so existing Solidity contracts and Ethereum tooling work. - **Configurable deployment models:** Deploy a public network with onchain data availability, or a private validium with offchain data availability and access control. - **Proven state transitions:** [zk-SNARK](/protocol/reference/zero-knowledge-glossary#zk-snark)**zk-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. proofs verify that state transitions are valid. A valid proof means the operator cannot finalize an invalid state transition through the normal proof path. - **Ethereum-anchored interoperability:** Bridge to Ethereum or Linea through rollup and bridge components. Trust assumptions depend on the deployment model, data availability design, and verifier configuration. - **Operational clarity and control:** Clearly defined components, responsibilities, and failure boundaries help you reason about trust, security, and compliance. Lineth is for technical operators and infrastructure teams who need to run their own network, including cases that need privacy, governance, or access controls that public networks do not provide. Start by [evaluating Lineth](/stack/evaluate) for your use case.