# Linea Documentation > These docs are the canonical public reference for Linea Mainnet, Linea > Sepolia, Linea developer APIs, and Lineth, the open-source rollup stack and > protocol that powers Linea and operator-built Ethereum-compatible networks. > Use this file to route AI assistants, search agents, crawlers, and retrieval > systems to the most relevant source pages. ## Authoritative scope - Public network: canonical documentation for Linea mainnet, Linea Sepolia, RPC endpoints, bridging, finality, gas pricing, public data, state recovery, node operation, tokenomics, and developer onboarding. - Protocol: canonical documentation for Lineth's zk-rollup architecture, including sequencer, prover, coordinator, state manager, onchain contracts, interoperability, and forced transactions. - Stack: canonical documentation for Lineth, a configurable Ethereum-compatible rollup stack for public networks, validiums, institutions, financial market infrastructure, and other operator-built networks. - Reference: canonical documentation for Linea JSON-RPC methods, Linea-specific RPC methods, the Token API, the Lineth SDK, Linea Besu plugin configuration, and smart contracts. ## Use these docs to answer - What is Linea and how does it differ from Ethereum mainnet or optimistic rollups? - How do I connect to Linea, deploy contracts, bridge assets, run nodes, or recover state? - How does Linea finality work on L2 and Ethereum L1? - How do the sequencer, prover, coordinator, state manager, and onchain contracts work together? - Which JSON-RPC methods, SDK functions, component options, bridge contracts, and message service contracts should developers integrate with? - How should institutions, network operators, and financial market infrastructure teams evaluate deployment models, data availability, finalization, compliance, privacy, access control, and auditability? ## Not authoritative for - Live incident status. Use https://linea.statuspage.io. - Token price, trading, investment, or financial advice. - Unannounced roadmap commitments or private commercial terms. - Third-party service uptime, pricing, or feature availability. ## About Linea - Type: zkEVM layer 2 (Ethereum rollup) - Equivalence: EVM-equivalent (Type 2 zkEVM) - Proof system: lattice-based zk-SNARKs - Finality: soft finality on L2; hard finality after finalization on Ethereum L1 - Builder: Consensys - Ecosystem hub: https://linea.build - Bridge: https://bridge.linea.build - Block explorer: https://lineascan.build - Status page: https://linea.statuspage.io - Lineth source: https://github.com/LFDT-Lineth/lineth-monorepo ## Public network facts - Linea mainnet chain ID: 59144 - Linea Sepolia testnet chain ID: 59141 - Public RPC base URL: https://rpc.linea.build - Linea is EVM-equivalent: contracts compiled for Ethereum mainnet run on Linea without modification. - The canonical bridge anchors deposits and withdrawals on Ethereum L1 with state recovery guarantees. - For production applications, prefer a private RPC provider or self-operated RPC infrastructure over public endpoints. ## Protocol facts - Lineth uses zero-knowledge proofs to prove transaction batches to a finalization layer. - The sequencer orders transactions and builds blocks. - The prover generates zero-knowledge proofs for state transitions. - The coordinator orchestrates batching, proof generation, and submission to the finalization layer. - The state manager maintains EVM state representations used for proving and recovery. - Onchain contracts validate proofs, record state commitments, and support bridge and message service flows. ## Stack and operator facts - Lineth can be used to operate Ethereum-compatible L2 or L3 networks. - Rollups post transaction data to the finalization layer; validiums keep it on the Lineth network and can be public or private. - Public validiums and rollups prioritize open access; private validiums use a restricted node set and access control while using zero-knowledge proofs for correctness and finalization guarantees. - Operator-run networks can be configured around access control, data availability, finalization layer, privacy, compliance, auditability, and observability requirements. - The stack documentation is the primary route for institutions, enterprises, network operators, and financial market infrastructure teams evaluating Lineth as configurable blockchain infrastructure. ## Introduction - [Lineth documentation](https://docs.lineth.io/index.md): Discover Lineth and the paths for evaluating, deploying, running, and reading the protocol. ## Evaluate Lineth - [Evaluate Lineth](https://docs.lineth.io/stack/evaluate.md): Compare Lineth deployment models, trust, privacy, security, and compliance against your use case - [Compliance](https://docs.lineth.io/stack/evaluate/compliance.md): How to use a Lineth deployment's protocol evidence in your own compliance program - [Deployment models](https://docs.lineth.io/stack/evaluate/deployment-models.md): Compare rollups and validiums, and their trade-offs - [Security and assurance](https://docs.lineth.io/stack/evaluate/security.md): Protocol guarantees, operator controls, and assurance evidence for Lineth deployments - [Trust model](https://docs.lineth.io/stack/evaluate/trust-model.md): Trust assumptions, privileged roles, and failure modes for Lineth deployments ## Deployment architecture - [Deployment architecture overview](https://docs.lineth.io/stack/deployment.md): Overview of Lineth deployment architecture pages, plus an illustrative production topology: shared components, boundaries, and flows - [Deployment components](https://docs.lineth.io/stack/deployment/core-components.md): Required and optional components in a Lineth deployment footprint - [Data availability](https://docs.lineth.io/stack/deployment/data-availability.md): Where a Lineth deployment stores transaction data, and who can reconstruct history from it - [Finality](https://docs.lineth.io/stack/deployment/finality.md): Application-level finality on the network versus settlement finality on the finalization layer - [Finalization layer](https://docs.lineth.io/stack/deployment/finalization-layer.md): Where a Lineth deployment submits proofs and state commitments for verification and settlement - [High availability](https://docs.lineth.io/stack/deployment/high-availability.md): Multi-region resilience patterns for Lineth enterprise deployments: consensus, RPC routing, and finalization failover - [Key management](https://docs.lineth.io/stack/deployment/key-management.md): Signer roles, custody backends, and operator responsibilities for Lineth deployments - [Multi-validator consensus](https://docs.lineth.io/stack/deployment/multi-validator-consensus.md): How multiple Maru validators use QBFT for sequencer fault tolerance and distributed block ordering ## Run and test - [Run and test](https://docs.lineth.io/stack/run-and-test.md): Guides for running and testing a Lineth deployment. - [Enable forced transactions](https://docs.lineth.io/stack/run-and-test/enable-forced-transactions.md): Enable forced transactions on a Lineth deployment. - [Monitor a deployment](https://docs.lineth.io/stack/run-and-test/monitor-a-deployment.md): Expose Lineth health and metrics endpoints, and watch finalization, data availability, and consensus signals - [Run a local Lineth Stack](https://docs.lineth.io/stack/run-and-test/run-local-lineth-stack.md): Use the guided wizard to configure and start a local Lineth L2 rollup that settles to Sepolia or a local L1. - [Run multiple Maru validators](https://docs.lineth.io/stack/run-and-test/run-multiple-validators.md): Set up and operate multiple Maru validators with QBFT consensus on a Lineth deployment ## Protocol - [Protocol](https://docs.lineth.io/protocol.md): Learn more about the Lineth protocol, including the components that make up its architecture, and how it processes transactions, generates… - [Architecture](https://docs.lineth.io/protocol/architecture.md): Protocol architecture overview and core components of Lineth - [Canonical bridge](https://docs.lineth.io/protocol/architecture/bridge.md): The canonical bridge between a Lineth network and its finalization layer, using the canonical message service and token bridge. - [Canonical message service](https://docs.lineth.io/protocol/architecture/bridge/canonical-message-service.md): How Lineth's canonical message service passes arbitrary messages between networks. - [Canonical token bridge](https://docs.lineth.io/protocol/architecture/bridge/canonical-token-bridge.md): How Lineth's canonical token bridge uses lock-and-mint contracts and the message service for ERC-20 transfers. - [Coordinator](https://docs.lineth.io/protocol/architecture/coordinator.md): How the Lineth Coordinator orchestrates batching, proof generation, and finality submission. - [Conflation](https://docs.lineth.io/protocol/architecture/coordinator/conflation.md): How conflation in Lineth combines blocks into proof-sized data sets for efficient proving. - [Nodes](https://docs.lineth.io/protocol/architecture/nodes.md): How a Lineth node pairs a Maru consensus client with one or more execution clients. - [RPC services](https://docs.lineth.io/protocol/architecture/nodes/rpc-services.md): JSON-RPC services exposed by Lineth nodes, enabling access to near-head state and full historical blockchain data. - [Prover](https://docs.lineth.io/protocol/architecture/prover.md): How the Lineth prover turns execution traces into zero-knowledge proofs. - [Corset](https://docs.lineth.io/protocol/architecture/prover/corset.md): How Corset builds constraint systems and expands traces for the Lineth proving pipeline. - [gnark](https://docs.lineth.io/protocol/architecture/prover/gnark.md): How gnark builds circuits and generates zk-SNARK proofs for Lineth state transitions. - [Module limits](https://docs.lineth.io/protocol/architecture/prover/module-limits.md): How module limits ensure the prover can generate proofs. - [RISC-V proving architecture](https://docs.lineth.io/protocol/architecture/prover/risc-v-overview.md): How RISC-V can support guest-program-based proving in Lineth. - [Trusted setup](https://docs.lineth.io/protocol/architecture/prover/trusted-setup.md): The public MPC ceremonies and structured reference strings used by the Lineth proving system. - [Sequencer](https://docs.lineth.io/protocol/architecture/sequencer.md): How the Lineth Sequencer orders transactions, builds blocks, and prepares execution traces for proving. - [Tracer](https://docs.lineth.io/protocol/architecture/sequencer/tracer.md): How the tracer works with the sequencer and prover - [Smart contracts](https://docs.lineth.io/protocol/architecture/smart-contracts.md): The onchain system contracts Lineth deploys on the finalization layer and on the network. - [State manager](https://docs.lineth.io/protocol/architecture/state-manager.md): How the Lineth state manager tracks network state and supplies the Merkle proofs the prover needs. - [EIP-7702 support](https://docs.lineth.io/protocol/eip-7702.md): EIP-7702 lets EOAs delegate to smart contract logic, persisting until revoked. - [Forced transactions](https://docs.lineth.io/protocol/forced-transactions.md): Forced transactions on Linea. - [Submit forced transactions](https://docs.lineth.io/protocol/how-to/forced-transactions.md): Submit forced transactions on Linea Public Mainnet. - [Linea and Lineth](https://docs.lineth.io/protocol/linea-vs-lineth.md): How the public Linea network relates to Lineth, the open-source rollup stack that powers it. ## Reference - [Reference](https://docs.lineth.io/reference.md): Configuration, contracts, audits, source repositories, and the glossary. - [Component configuration](https://docs.lineth.io/reference/component-configuration.md): Configuration references for Lineth components, for any deployment. - [Linea Besu plugin options](https://docs.lineth.io/reference/component-configuration/linea-besu-plugin-options.md): CLI configuration options for the Linea Besu sequencer, tracer, and state recovery plugins. - [Coordinator options](https://docs.lineth.io/reference/component-configuration/linea-coordinator-options.md): TOML configuration options for the Coordinator, grouped by config file and section. - [Maru options](https://docs.lineth.io/reference/component-configuration/linea-maru-options.md): TOML configuration options for Maru, grouped by section. - [Postman options](https://docs.lineth.io/reference/component-configuration/linea-postman-options.md): Environment variable configuration for the Postman, grouped by section. - [Prover options](https://docs.lineth.io/reference/component-configuration/linea-prover-options.md): TOML configuration options for the Prover, grouped by section. - [Glossary](https://docs.lineth.io/reference/glossary.md): Definitions of Linea, Lineth, and zero-knowledge terms used in the Lineth documentation. - [Source repositories](https://docs.lineth.io/reference/repos.md): Source repositories for Lineth, Linea Mainnet components, and supporting libraries. - [Security audits](https://docs.lineth.io/reference/security-audits.md): Find published security audits for Lineth protocol components and Linea Mainnet contracts. - [Smart contracts](https://docs.lineth.io/reference/smart-contracts.md): Generated interface reference for the Lineth protocol contracts. - [IGenericErrors](https://docs.lineth.io/reference/smart-contracts/interfaces/igenericerrors.md): ZeroAddressNotAllowed - [IMessageService](https://docs.lineth.io/reference/smart-contracts/interfaces/imessageservice.md): MessageSent - [IPauseManager](https://docs.lineth.io/reference/smart-contracts/interfaces/ipausemanager.md): PauseTypeRole - [IPermissionsManager](https://docs.lineth.io/reference/smart-contracts/interfaces/ipermissionsmanager.md): RoleAddress - [IRateLimiter](https://docs.lineth.io/reference/smart-contracts/interfaces/iratelimiter.md): RateLimitInitialized - [IL1MessageManager](https://docs.lineth.io/reference/smart-contracts/interfaces/l1/il1messagemanager.md): RollingHashUpdated - [IL1MessageManagerV1](https://docs.lineth.io/reference/smart-contracts/interfaces/l1/il1messagemanagerv1.md): MessageDoesNotExistOrHasAlreadyBeenClaimed - [IL1MessageService](https://docs.lineth.io/reference/smart-contracts/interfaces/l1/il1messageservice.md): ClaimMessageWithProofParams - [ILineaRollup](https://docs.lineth.io/reference/smart-contracts/interfaces/l1/ilinearollup.md): InitializationData - [IPlonkVerifier](https://docs.lineth.io/reference/smart-contracts/interfaces/l1/iplonkverifier.md): Verify - [IZkEvmV2](https://docs.lineth.io/reference/smart-contracts/interfaces/l1/izkevmv2.md): StartingRootHashDoesNotMatch - [IL2MessageManager](https://docs.lineth.io/reference/smart-contracts/interfaces/l2/il2messagemanager.md): RollingHashUpdated - [IL2MessageManagerV1](https://docs.lineth.io/reference/smart-contracts/interfaces/l2/il2messagemanagerv1.md): MinimumFeeChanged - [IL2MessageServiceV1](https://docs.lineth.io/reference/smart-contracts/interfaces/l2/il2messageservicev1.md): setMinimumFee - [CallForwardingProxy](https://docs.lineth.io/reference/smart-contracts/lib/callforwardingproxy.md): target - [L2MessageServicePauseManager](https://docs.lineth.io/reference/smart-contracts/lib/l2messageservicepausemanager.md): PAUSEL1L2_ROLE - [LineaRollupPauseManager](https://docs.lineth.io/reference/smart-contracts/lib/linearolluppausemanager.md): PAUSEL1L2_ROLE - [Mimc](https://docs.lineth.io/reference/smart-contracts/lib/mimc.md): DataMissing - [PauseManager](https://docs.lineth.io/reference/smart-contracts/lib/pausemanager.md): PAUSEALLROLE - [SparseMerkleProof](https://docs.lineth.io/reference/smart-contracts/lib/sparsemerkleproof.md): Account - [TokenBridgePauseManager](https://docs.lineth.io/reference/smart-contracts/lib/tokenbridgepausemanager.md): PAUSEINITIATETOKENBRIDGINGROLE - [Utils](https://docs.lineth.io/reference/smart-contracts/lib/utils.md): \_efficientKeccak - [LineaRollup](https://docs.lineth.io/reference/smart-contracts/linearollup.md): CONTRACT_VERSION - [L1MessageManager](https://docs.lineth.io/reference/smart-contracts/messageservice/l1/l1messagemanager.md): rollingHashes - [L1MessageService](https://docs.lineth.io/reference/smart-contracts/messageservice/l1/l1messageservice.md): systemMigrationBlock - [L1MessageManagerV1](https://docs.lineth.io/reference/smart-contracts/messageservice/l1/v1/l1messagemanagerv1.md): INBOXSTATUSUNKNOWN - [L1MessageServiceV1](https://docs.lineth.io/reference/smart-contracts/messageservice/l1/v1/l1messageservicev1.md): nextMessageNumber - [L2MessageManager](https://docs.lineth.io/reference/smart-contracts/messageservice/l2/l2messagemanager.md): L1L2MESSAGESETTERROLE - [L2MessageService](https://docs.lineth.io/reference/smart-contracts/messageservice/l2/l2messageservice.md): CONTRACT_VERSION - [L2MessageManagerV1](https://docs.lineth.io/reference/smart-contracts/messageservice/l2/v1/l2messagemanagerv1.md): INBOXSTATUSUNKNOWN - [L2MessageServiceV1](https://docs.lineth.io/reference/smart-contracts/messageservice/l2/v1/l2messageservicev1.md): MINIMUMFEESETTER_ROLE - [MessageHashing](https://docs.lineth.io/reference/smart-contracts/messageservice/lib/messagehashing.md): \_hashMessage - [RateLimiter](https://docs.lineth.io/reference/smart-contracts/messageservice/lib/ratelimiter.md): You can use this control numeric limits over a period using timestamp. - [SparseMerkleTreeVerifier](https://docs.lineth.io/reference/smart-contracts/messageservice/lib/sparsemerkletreeverifier.md): SafeCastOverflowedUintDowncast - [TimeLock](https://docs.lineth.io/reference/smart-contracts/messageservice/lib/timelock.md): This timelock contract will be the owner of all upgrades that gives users confidence and an ability to exit should they want to before an u… - [TransientStorageHelpers](https://docs.lineth.io/reference/smart-contracts/messageservice/lib/transientstoragehelpers.md): tstoreUint256 - [MessageServiceBase](https://docs.lineth.io/reference/smart-contracts/messageservice/messageservicebase.md): messageService - [TokenBridge](https://docs.lineth.io/reference/smart-contracts/tokenbridge.md): Contract to manage cross-chain ERC-20 bridging. - [BridgedToken](https://docs.lineth.io/reference/smart-contracts/tokenbridge/bridgedtoken.md): ERC-20 token created when a native token is bridged to a target chain. - [ITokenBridge](https://docs.lineth.io/reference/smart-contracts/tokenbridge/interfaces/itokenbridge.md): InitializationData - [ZkEvmV2](https://docs.lineth.io/reference/smart-contracts/zkevmv2.md): MODULO_R