linea.build valid

Linea Documentation

These docs are the canonical public reference for Linea Mainnet, Linea

For agents: Canonical public docs for Linea Mainnet and Linea Sepolia, a zkEVM L2 on Ethereum: network connection, RPC, block explorers, token bridge and contracts.

lineazkevm layer 2ethereumrpcblock explorertoken bridge

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T17:03:49.098Z. Cached copy · Source on linea.build

# 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
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=linea.build · GET /v1/domain/linea.build · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for linea.build:
1. POST https://agentwebmap.com/v1/sites/linea.build/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://linea.build/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/linea.build/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/linea.build).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.