agentleFS
ConsensysConsensys/doc.linea/static/llms.txt

doc.linea / static

llms.txt478 starsChanged 3 months agoApache-2.0View on GitHub

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.

Files
llms.txt
# 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.

## Quickstart and onboarding
- [Network quickstart](https://docs.linea.build/network/quickstart): Get started building on Linea, including network endpoints, wallet setup, and first deploys.
- [Network overview](https://docs.linea.build/network/overview): What Linea is, the security and equivalence guarantees, and core network features.
- [Reference](https://docs.linea.build/reference): Entry point for APIs, SDKs, component configuration, and smart contracts.
- [RPC and API overview](https://docs.linea.build/api/quickstart): Linea JSON-RPC and Token API entry point.
- [Protocol quickstart](https://docs.linea.build/protocol/quickstart): Entry point for protocol architecture, prover, sequencer, and coordinator details.
- [Stack overview](https://docs.linea.build/stack): Entry point for operators evaluating and deploying with Lineth.

## Network features
- [Transaction finality](https://docs.linea.build/network/overview/transaction-finality): How and when transactions are final on Linea and on Ethereum L1.
- [Predictable pricing](https://docs.linea.build/network/overview/predictable-pricing): Linea's gas pricing model and fee components.
- [Public data](https://docs.linea.build/network/overview/public-data): What data is published on L1 and how to access it.
- [Recoverable state](https://docs.linea.build/network/overview/recoverable-state): The guarantees that allow Linea state to be recovered without trusted operators.
- [Differences from Ethereum](https://docs.linea.build/network/overview/ethereum-differences): Concrete behavioural differences developers must account for.
- [Yield Boost](https://docs.linea.build/network/overview/yield-boost): Native ETH yield mechanism and risk disclosures.

## Build on Linea
- [Build overview](https://docs.linea.build/network/build): Index of build guides, tools, and references.
- [Launch an app](https://docs.linea.build/network/build/launch-an-app): End-to-end path from deploy to listing in the Linea Hub.
- [Connect to Linea](https://docs.linea.build/network/build/connect): RPC endpoints and chain IDs (mainnet 59144, Sepolia testnet 59141).
- [Block explorers](https://docs.linea.build/network/build/block-explorers): Lineascan and other explorers.
- [Bridge](https://docs.linea.build/network/build/bridge): The canonical Linea bridge to and from Ethereum.
- [Smart contracts](https://docs.linea.build/network/build/contracts): Pre-deployed contracts, addresses, and verified code.
- [Get testnet ETH](https://docs.linea.build/network/build/get-testnet-eth): Faucets and testnet onboarding.
- [Send and receive messages](https://docs.linea.build/network/build/send-receive-messages): Cross-chain messaging on Linea.
- [Tools](https://docs.linea.build/network/build/tools): Account abstraction, indexing, paymasters, and developer tooling.

## How-to guides
- [Recover state](https://docs.linea.build/network/how-to/recover-state)
- [Estimate gas costs](https://docs.linea.build/network/how-to/gas-fees)
- [Bridge tokens to Linea](https://docs.linea.build/network/how-to/bridge)
- [Connect a wallet to your dapp](https://docs.linea.build/network/how-to/connect-wallet)
- [Deploy a smart contract](https://docs.linea.build/network/how-to/deploy-smart-contract): Hardhat, Foundry, Remix, thirdweb, Cookbook, Atlas.
- [Verify a smart contract](https://docs.linea.build/network/how-to/verify-smart-contract): Hardhat, Foundry, Atlas.
- [Run a node](https://docs.linea.build/network/how-to/run-a-node): Linea Besu, Maru, Besu, Geth, Erigon, plus bootnodes and migration guides.
- [Migrate a dapp](https://docs.linea.build/network/how-to/migrate-dapp)
- [Add an RPC fallback](https://docs.linea.build/network/how-to/fallback)
- [Verify users with Proof of Humanity](https://docs.linea.build/network/how-to/verify-users-with-proof-of-humanity)
- [Write and deploy assertions](https://docs.linea.build/network/how-to/write-and-deploy-assertions)

## Tutorials
- [Build an AI agent on Linea](https://docs.linea.build/network/tutorials/aiagent-quickstart)
- [Build your first dapp](https://docs.linea.build/network/tutorials/first-dapp)
- [Build a marketplace dapp](https://docs.linea.build/network/tutorials/marketplace-dapp)
- [Build a voting dapp](https://docs.linea.build/network/tutorials/voting-dapp)
- [Upgrade an EOA to a smart account (EIP-7702)](https://docs.linea.build/network/tutorials/eip-7702)
- [Ecosystem tutorials, including USDC](https://docs.linea.build/network/tutorials/ecosystem-tutorials)

## Reference
- [JSON-RPC API overview](https://docs.linea.build/api/reference): Index of every supported JSON-RPC method on rpc.linea.build.
- [Linea SDK](https://docs.linea.build/api/linea-sdk): TypeScript SDK for cross-chain messaging and bridge claim flows.
- [Token API](https://docs.linea.build/api/token-api): Token metadata and balance API reference.
- [Linea Besu plugin options](https://docs.linea.build/reference/component-configuration/linea-besu-plugin-options): CLI configuration options for Linea Besu plugins.
- [Maru options](https://docs.linea.build/reference/component-configuration/linea-maru-options): TOML configuration options for Maru.
- Linea-specific JSON-RPC methods:
  - [linea_estimateGas](https://docs.linea.build/api/reference/linea-estimategas)
  - [eth_sendBundle](https://docs.linea.build/api/reference/eth-sendbundle)
  - [eth_sendRawTransaction](https://docs.linea.build/api/reference/eth-sendrawtransaction)
  - [linea_getProof](https://docs.linea.build/api/reference/linea-getproof)
  - [linea_getTransactionExclusionStatusV1](https://docs.linea.build/api/reference/linea-gettransactionexclusionstatusv1)
- Smart contract reference:
  - [LineaRollup](https://docs.linea.build/api/linea-smart-contracts/linearollup)
  - [zkEVM v2](https://docs.linea.build/api/linea-smart-contracts/zkevmv2)
  - [Token bridge](https://docs.linea.build/api/linea-smart-contracts/tokenbridge)
  - [Message service](https://docs.linea.build/api/linea-smart-contracts/messageservice)

## Protocol
- [Architecture overview](https://docs.linea.build/protocol/architecture): Core components and how they interact.
- [Sequencer](https://docs.linea.build/protocol/architecture/sequencer): Block building, traces generation, conflation.
- [Prover](https://docs.linea.build/protocol/architecture/prover): Circuit building, proving pipeline, prover limits.
- [State manager](https://docs.linea.build/protocol/architecture/state-manager): EVM state representation in the rollup.
- [Smart contracts](https://docs.linea.build/protocol/architecture/smart-contracts): On-L1 contracts that anchor Linea.
- [Coordinator](https://docs.linea.build/protocol/architecture/coordinator): Orchestrates sequencing, proving, and finalisation.
- [Interoperability](https://docs.linea.build/protocol/architecture/interoperability): Canonical token bridge and message service.
- [RPC services](https://docs.linea.build/protocol/architecture/rpc-services): RPC topology, scaling, and operational design.
- [Forced transactions](https://docs.linea.build/protocol/forced-transactions): Censorship-resistance via L1-forced inclusion.
- [EIP-7702 on Linea](https://docs.linea.build/protocol/eip-7702): Account-abstraction support for EOAs.
- [Tokenomics](https://docs.linea.build/network/overview/tokenomics): The LINEA token, supply, distribution, and burn mechanics.
- [Glossary of Linea, Lineth, and zero-knowledge terms](https://docs.linea.build/protocol/reference/zero-knowledge-glossary)
- [Linea repositories](https://docs.linea.build/protocol/reference/repos)

## Lineth for operators
- [Stack overview](https://docs.linea.build/stack): What Lineth is and who it is for.
- [Evaluate Lineth](https://docs.linea.build/stack/evaluate): Evidence paths for evaluating a Lineth deployment.
- [Deployment models](https://docs.linea.build/stack/evaluate/deployment-models): Rollup, public validium, and private validium deployment trade-offs.
- [Trust model](https://docs.linea.build/stack/evaluate/trust-model): Trust assumptions, authority, and failure boundaries.
- [Privacy and data visibility](https://docs.linea.build/stack/evaluate/validium): What a private validium publishes, retains on the Lineth network, and allows participants to verify.
- [Security and assurance](https://docs.linea.build/stack/evaluate/security): Protocol guarantees, operator controls, and assurance evidence.
- [Compliance](https://docs.linea.build/stack/evaluate/compliance): Protocol evidence operators can use in a compliance program, and what Lineth does not claim.
- [Deployment architecture](https://docs.linea.build/stack/deployment): Components, data availability, finalization layer, finality, and access control.
- [Deployment components](https://docs.linea.build/stack/deployment/core-components): Required and optional operator footprint.
- [Data availability](https://docs.linea.build/stack/deployment/data-availability): Validium versus rollup models, and public versus private validium.
- [Finalization layer](https://docs.linea.build/stack/deployment/finalization-layer): Where proofs and state commitments settle.
- [Finality](https://docs.linea.build/stack/deployment/finality): Application-level and settlement finality choices.
- [Multi-validator consensus](https://docs.linea.build/stack/deployment/multi-validator-consensus): Maru QBFT design, fault-tolerance scope, topology, and latency trade-offs.
- [Access control](https://docs.linea.build/stack/deployment/access-control): Operator-configured access policy for protected surfaces.
- [Lineth-to-Lineth interoperability](https://docs.linea.build/stack/deployment/interoperability): Peer Lineth calls; a restricted destination authorizes them against access control.
- [Run a local Lineth Stack](https://docs.linea.build/stack/how-to/run-local-lineth-stack): Non-production local Stack workflow.
- [Run multiple Maru validators](https://docs.linea.build/stack/how-to/run-multiple-validators): Run multiple Maru validators with QBFT.
- [Enable forced transactions](https://docs.linea.build/stack/how-to/enable-forced-transactions): Enable forced transactions on a Lineth deployment (not yet live).

## Changelog and risk
- [Changelog and release notes](https://docs.linea.build/changelog/release-notes): Network upgrades and deployments by date.
- [Risk disclosures](https://docs.linea.build/network/risk-disclosures): Known risks for users and integrators.

## Authoring and licensing
- Source repository for these docs: https://github.com/Consensys/doc.linea
- Docs licence: see repository LICENSE

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.