Layer 2 blockchain · settles to Ethereum
Linea ticker ETH
Summary
Zero-knowledge rollup on Ethereum. Since Beta v4.0 (October 2025) blocks come from a sequencer node that pairs Maru, a consensus client using the QBFT algorithm that replaced the earlier Clique proof-of-authority setup, with a Linea Besu execution client; Linea says only one Linea-internal Maru node produces blocks for now. A coordinator groups blocks into batches and posts compressed data to Ethereum as blobs. A prover makes zk-SNARK proofs (L2BEAT describes a recursive PLONK-based stack that relies on trusted setups), and a contract on Ethereum verifies each proof and records the finalized state root. Block production uses no stake or work of its own. 3451416171825
Design
- System
- Layer 2 blockchainLinea Mainnet (chain ID 59144) is a zero-knowledge (validity-proof) rollup on Ethereum, incubated within Consensys and built on the open-source Lineth stack (formerly the Linea stack), which was contributed to Linux Foundation Decentralized Trust in May 2026. ETH is the gas asset. The LINEA token pays no gas and, per Linea's tokenomics page, carries no governance rights, so the display name uses ETH.
- Settles to
- EthereumCompressed batch data goes to Ethereum as blobs, and a batch is final once a verifier contract on Ethereum accepts its proof and that Ethereum block is finalized; Linea gives a median of about 2 hours to this hard finality and says it should not exceed 16 hours in normal operation. Withdrawals have no fraud-proof challenge window, but they wait for that finality and then need a claim on Ethereum; Linea's bridge guide gives 2 to 12 hours. Users cannot yet force transactions through Ethereum, and after six months without finalization the operator role opens to anyone, per L2BEAT.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Other
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- One sequencer maintained by the Linea team: Linea's Maru guide says only one Linea-internal Maru node produces blocks, and its risk disclosures call the sequencer and prover centralized components maintained by the Linea team during the Beta. L2BEAT lists two whitelisted operator accounts that may prove blocks and post data. Forced transactions through Ethereum are designed and staged in the rollup contract, but Linea says they are not yet live; L2BEAT says the operator role opens to anyone only after six months without finalized blocks.
- Fork choice
- No open L2 fork choice: Linea's node guide says node operators have no option to vote on blocks or take part in fork choice. Linea says a transaction sealed into an L2 block will not be removed or reordered by Linea, which is an operator promise; the Ethereum-backed guarantee comes only when the batch's proof is verified on Ethereum and that Ethereum block is finalized.
Qualifications
- Scarce resource · Not applicable. Linea block production uses no stake or work of its own; the sequencer is a single operator-run QBFT validator, and security comes from Ethereum plus validity proofs.
- Finality · Partial. Linea documents soft finality when the sequencer seals a block (about one second, which Linea calls its block time) and hard finality when the proof is verified on Ethereum and that block is finalized (median about 2 hours). Only the second is backed by Ethereum, so the standard finality categories do not fit.
- Upgrade authority · Applies. A 5-of-9 Security Council can pause the rollup and upgrade the core contracts immediately, with no delay, per Linea's risk disclosures, its Security Council transaction record and L2BEAT. Since Beta v5.2 (April 2026) an Emergency Pauser account run by Linea's security operations team can also pause the core contracts, but only for a limited time: L2BEAT gives two days followed by a two-day cooldown. Member identities are not published in the record.
- Withdrawal window · Applies. No fraud-proof challenge period applies. Withdrawals to Ethereum wait for proof-verified finality and a manual claim on Ethereum; Linea's bridge guide gives 2 to 12 hours, while its network overview says funds can be withdrawn instantly and at no cost, which does not match the bridge guide.
- Native token role · Not applicable. LINEA pays no gas and has no governance rights, per Linea's tokenomics page; surplus fee revenue is burned, 20% as ETH and 80% as LINEA bought with that revenue.
- Bridge collateral staking · Applies. Yield Boost lets ETH in the bridge contract above a withdrawal reserve be staked through a Lido V3 vault. Linea announced it as activated with Beta v5.1 on 30 March 2026, but its Security Council record shows the Lido vault was created on 17 April 2026 and the staking allowance then raised in steps: 20 basis points on 21 April, up to 10% of funds on 14 July and up to 60% on 1 September 2026, when the target unstaked reserve was cut to 40%. How much is actually staked was not measured. Rewards go to Linea ecosystem incentives, not to depositors.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Decentralized operation and upgrade safety: one sequencer maintained by the Linea team orders all transactions and can delay or reorder them, users cannot yet force transactions in through Ethereum, and a 5-of-9 Security Council can pause the rollup and upgrade its contracts immediately, with no exit window, per Linea's risk disclosures and L2BEAT, which rates Linea Stage 0.The security emphasis means every state update must pass a validity proof on Ethereum and batch data is posted there, so state can be rebuilt from Ethereum. That rests on sound circuits, trusted setups and correct verifiers: L2BEAT says the latest verifier upgrade had not been independently reproduced, and in September 2026 the council replaced a verifier to fix cases where proofs could not be generated. Since April 2026 part of the ETH held by the bridge contract has been staked on Ethereum through a Lido V3 vault, which adds staking and Lido dependencies.
- Full node at home
- Practical at home 45673536Linea's Besu guides give about 509 GB for a full node, growing about 9 MB a day, and about 3.9 TB for an archive node (figures last updated 3 November 2025); CPU, RAM and bandwidth minimums are not stated. Every node runs Maru beside an execution client; Docker Compose is recommended. An Ethereum RPC endpoint is optional: Linea's mainnet Maru configuration enables it only for the finalized block tag, and the Linea Besu guide asks for one only in its advanced profile. A home node only follows the sequencer, with no incentives and no vote on blocks.
- Throughput claims
- Theoretical peak: 200 18Theoretical peak; not comparable across chains or with observed load.Million gas per second (Mgas/s), as stated by Linea; not transactions per second.Stated in Linea's release notes for Beta v5.2 (mainnet 1 April 2026): the release increases throughput to 200 Mgas/s.Linea-operated sequencer and prover infrastructure; hardware not stated.Team-stated capacity, not an observed rate of use; the release note gives no method, test window or measured load. Gas per second is not transactions per second; the gas used by a transaction varies widely. The release note does not say whether sequencing, proving or data posting to Ethereum sets the limit. Ignores state growth, propagation to follower nodes and whether a home node can keep up at that rate. Ethereum-backed finality still waits for proof verification, which Linea gives as about 2 hours at the median.
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | A protocol-level trust-minimized swap mechanism on Linea was not reviewed; EVM contracts could implement hash-locked swaps, but none was verified. |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Built into the protocolLimited scope | Linea's rollup protocol produces what a light verifier checks: a finalized state root is recorded on Ethereum only after a validity proof passes, and Linea serves account and storage proofs for finalized blocks from its sparse Merkle tree, so anyone following Ethereum can check Linea state against that root. Limited: only finalized blocks (hard finality) can be checked this way, the proofs do not use Ethereum's state-proof format, and no dedicated Linea light client was reviewed. 31011 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to Linea was reviewed. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Linea runs EVM contracts with Ethereum tooling, with documented differences such as no blob transactions and a call data cap. Since Beta v5.0 (March 2026) it supports EIP-7702, so ordinary accounts can delegate to smart-account code for batching, sponsored gas or session keys. 121318 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; no protocol feature to cancel or delay a sent payment or to recover an account was found. Linea's EIP-7702 page lists social recovery among the smart-account features ordinary accounts can now use, but no recovery product live on Linea was reviewed. 13 |
| Rollups | Unknown | Rollups anchored to Linea were not reviewed. Linea says others can deploy the Lineth stack as their own L2 or L3 networks, but those are separate from Linea Mainnet. Linea itself is a rollup on Ethereum; see the mechanism and Ethereum dependency notes. |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Established in the ecosystemEtherex, SyncSwap | Etherex describes itself as a concentrated-liquidity exchange built on Linea by the Linea and NILE teams and lists its contracts on Linea; SyncSwap's docs list its Linea pool factories, vault and routers. Liquidity depth and current activity were not measured, and other venues were not reviewed. 282930 |
| Issuer-native stablecoins | Established in the ecosystemUSDC (Circle), MetaMask USD (mUSD) | Circle lists natively issued USDC on Linea (0x176211869cA2b568f2A7D4EE941E073a821EE1ff), and Linea's bridge guide says USDC moves through Circle's Cross-Chain Transfer Protocol. MetaMask USD, issued with Bridge (a Stripe company) on the M0 protocol and described by MetaMask as backed by short-term US Treasury bills, launched on Ethereum and Linea in September 2025. Native here means issuer-issued on Linea, not a protocol asset; reserves were not reviewed. 223132 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on Linea were not reviewed. |
| Bridges | Native to the protocolLinea canonical bridge (message service and token bridge), Circle CCTP for USDC, LI.FI-powered aggregator in Linea's bridge app | ETH moves as value on the canonical message service and ERC-20 tokens through a lock-and-mint token bridge; messages to Ethereum can be claimed only after their batch is finalized, and anyone can submit the claim. Linea's bridge guide gives about 20 minutes into Linea and 2 to 12 hours out, with a manual claim on Ethereum for withdrawals and all USDC transfers. Third-party bridges were not reviewed individually. Risk: A 5-of-9 Security Council can pause and upgrade the bridge immediately; a Linea-run Emergency Pauser can pause it for a limited time. Forced transactions are not live, so a stalled or censoring operator can freeze withdrawals until L2BEAT's six-month fallback. Withdrawals are capped at 10,000 ETH a day on Ethereum and 8,000 ETH a day on Linea (council, April 2026). Since April 2026 part of the bridge's ETH is staked through Lido V3 (up to 60% from September 2026), so exits can wait on Ethereum's validator queue, with slashing and contract risk. 1718192021222325 |
| Block explorers | Established in the ecosystemLineascan (built by Etherscan), Blockscout (explorer.linea.build), Lineaplorer, OKLink, Linea for Humans | Linea's docs name Lineascan and a Blockscout instance as official explorers and list three community explorers that Linea says it has not audited or endorsed; only the two official ones were opened in this review. Explorer indexes are not canonical consensus. 242627 |
| Hardware wallets | ThinLedger Wallet (Linea behind a default-off feature switch), Trezor Safe 3, 5 and 7 (through MetaMask or Rabby) | See custody rows: Ledger Wallet's code includes Linea behind a feature switch that is off by default, with no Ledger page confirming users can open it; Trezor's Linea page lists the network, but Trezor Suite's own network configuration does not include Linea, so Trezor use goes through third-party wallet apps. Linea's EIP-7702 page warns that some hardware wallets could not sign smart-account authorizations as of March 2026. 13333439 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | PartialSame as native: Unknown | Can: Possibly hold and send ETH on Linea in Ledger Wallet: Ledger's current wallet code includes Linea as an Ethereum-family network, but behind a feature switch that is off by defaultCounted as limited first-party support under the shared custody rule: Ledger Wallet hides Linea unless its feature switch is on, the switch is off by default in code, and Ledger's remote switch setting could not be read. Ledger's Linea coin page returned 404 and its support article did not render, so no user-facing Ledger statement confirms the network is on. Linea's connection page names Ledger among supported wallets. Token and smart-account coverage were not reviewed. 2383940 |
| Trezor | Through an intermediaryMetaMask or Rabby (third-party wallet apps named on Trezor's Linea page)Same as native: Unknown | Can: Use a Trezor Safe 3, Safe 5 or Safe 7 on the Linea network through MetaMask or Rabby, confirming transactions on the device; Trezor's Linea page lists the Linea network for these models Cannot: Add a Linea network account in Trezor Suite: the EVM network list in Trezor Suite's public source code does not include Linea, although Trezor's Linea page names Trezor Suite as a compatible appTrezor's evidence conflicts: its Linea page lists Ethereum and Linea as networks and names Trezor Suite, but Suite's network configuration lists no Linea chain. The page may describe the LINEA token, which also exists on Ethereum. Older Trezor models were not reviewed. 3334 |
Public data
iKnow Blockchain has no public-data lookups for Linea yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Linea Besu v2.3.0 node package released with sequencer changes for tracing and forced transactions
The Lineth project published version 2.3.0 of the Linea Besu package, which bundles the Besu execution client with Linea's sequencer, tracer and Shomei plugins. The sequencer gains a setting to stop Linea's bespoke tracing at a configured time, and a fix removes duplicate forced transactions from its pool. The changelog also lists a Besu upgrade to 26.8.1 for Vert.x 5 and newer Teku libraries, though the release's own module table lists linea-besu 26.7.0-efa817c; the release does not explain the difference.
- Implementation:Tracing cut-off setting and forced-transaction pool deduplication implemented in the sequencer plugin
- Release:Linea Besu package v2.3.0 published on GitHub 23 September 2026, not marked pre-release
- Activation:No tracing cut-off time published; forced transactions not live per Linea's docs
Sources: Lineth (GitHub) — Linea Besu v2.3.0 (external site) · Lineth (GitHub) — Coordinator v1.2.0 (external site) · Linea Documentation — Forced transactions (external site) · Linea Documentation — Prover (external site) · Lineth (GitHub) — lineth-monorepo releases (external site)
-
Maru v1.4.0 consensus client released with Amsterdam support
The Lineth project published Maru v1.4.0, the consensus client every Linea node runs beside its execution client. The release adds support for Amsterdam, support for the Noise and Yamux peer-to-peer protocols and support for custom validator signers, fixes a build race, and renames internal code packages to the Lineth name. The release notes do not tie it to a Linea network upgrade, and Linea's release notes list no Amsterdam upgrade for Linea Mainnet at review time.
- Implementation:Amsterdam support, Noise and Yamux networking, and custom validator signers implemented in Maru
- Release:Maru v1.4.0 published on GitHub 23 September 2026, not marked pre-release
- Activation:No Linea network activation announced; Linea's release notes list no Amsterdam upgrade at review time
Sources: Lineth (GitHub) — Maru v1.4.0 (external site) · Lineth (GitHub) — lineth-monorepo releases (external site) · Linea Documentation — Maru (external site) · Linea Documentation — Release notes (external site)
-
Linea Besu v2.2.0 node package released on Besu 26.8.0
The Lineth project published version 2.2.0 of the Linea Besu package, the Besu execution client bundled with Linea's sequencer, tracer, state-recovery and Shomei plugins. The release adds support for custom liveness signers in Linea Besu, updates the bundled Besu client to 26.8.0, and tidies logging and image builds. It is a client release for node operators, not a network upgrade, and it was followed a month later by v2.3.0.
- Implementation:Custom liveness signer support and a Besu 26.8.0 update in the Linea Besu package
- Release:Linea Besu package v2.2.0 published on GitHub 24 August 2026, not marked pre-release; superseded by v2.3.0
- Activation:Not tied to a network activation; applies to a node when its operator installs it
Sources: Lineth (GitHub) — Linea Besu v2.2.0 (external site) · Lineth (GitHub) — lineth-monorepo releases (external site)
-
Rollup contract upgrade added forced-transaction support, which is not yet live
On 14 July 2026 the Security Council upgraded Linea's rollup contract on Ethereum from version 7.1 to 8.0, adding support for future forced transactions and setting a forced-transaction fee of 0.001 ETH. Forced transactions would let a user submit a Linea transaction through Ethereum with a processing deadline, after which a batch that skipped it could not be finalized. Linea's docs still say the feature is not yet live.
- Implementation:contract support deployed in rollup contract version 8.0
- Release:rollup contract version 8.0
- Activation:not live, per Linea's forced-transactions page
Sources: Linea Documentation — Linea Security Council transaction record (external site) · Linea Documentation — Forced transactions (external site) · L2BEAT — Linea (external site)
-
Linea's rollup stack was contributed to Linux Foundation Decentralized Trust as Lineth
Linux Foundation Decentralized Trust announced that the Linea Consortium joined as a premier member and contributed the open-source ZK rollup stack behind Linea, renamed Lineth, as its newest code project under vendor-neutral governance; Linea's post calls it an incubating project. The announcement says the same team keeps building it; neither it nor Linea's own post describes changes to how Linea Mainnet is operated.
- Implementation:code contributed and repository moved to the Lineth organization
- Release:not a software release
- Activation:incubating project at Linux Foundation Decentralized Trust
Sources: Linux Foundation Decentralized Trust — Linea Consortium Becomes Premier Member of Linux Foundation Decentralized Trust; Contributes Linea Stack as Newest Code Project (external site) · Linea — Building a credible neutral infrastructure: Linea Stack joins Linux Foundation Decentralized Trust as Lineth (external site) · Linea Documentation — Linea and Lineth (external site) · Lineth (GitHub) — LFDT-Lineth/lineth-monorepo (external site)
-
Yield Boost activated: part of the ETH held by Linea's bridge can now be staked
Linea announced Yield Boost as activated with Beta v5.1 on 30 March 2026. It lets ETH held by the rollup's bridge contract above a withdrawal reserve be staked on Ethereum through a Lido V3 vault, with net rewards directed to Linea ecosystem incentive programs. Linea's post planned a 96 ETH test first; the Security Council record shows the Lido vault was created on 17 April 2026, and the staking allowance was later raised to up to 10% of funds on 14 July 2026 and up to 60% on 1 September 2026.
- Implementation:Lido V3 staking vault and yield manager deployed
- Release:Beta v5.1
- Activation:Lido vault created 17 April 2026; allowance raised to up to 60% of funds on 1 September 2026
Sources: Linea — Yield Boost is Activated (external site) · Linea Documentation — Release notes (external site) · Linea Documentation — Yield Boost (external site) · Linea Documentation — Yield Boost risk disclosures (external site) · Linea Documentation — Linea Security Council transaction record (external site)
-
Beta v4.0 replaced Clique with the Maru consensus client and brought Linea up to Ethereum's Pectra rules
Linea's Beta v4.0 release, rolled out on mainnet in phases between 22 and 28 October 2025, introduced Maru, a consensus client using the QBFT algorithm, in place of the Clique proof-of-authority mechanism, and applied about four years of Ethereum upgrades up to the Pectra hard fork. Maru's mainnet configuration starts QBFT at the first (Paris) phase with a single validator. Since then every Linea node runs Maru beside its execution client.
- Implementation:Maru consensus client released and required for nodes
- Release:Beta v4.0
- Activation:Maru QBFT block production from the Paris phase on 22 October 2025; release complete with the Prague phase on 28 October 2025
Sources: Linea Documentation — Release notes (external site) · Linea Documentation — Maru (external site) · Linea Documentation — Run a Linea node (external site) · Linea Documentation — Besu (external site) · Lineth (GitHub) — Maru Linea Mainnet genesis configuration (linea-mainnet-genesis.json) (external site)
Topics your AI can explain
Your AI can explain these topics for Linea through the connection, with sources.
Known gaps
What this profile's review did not establish:
- The legal entity that operates the sequencer and prover, and the identities of the Security Council members, were not sourced; Linea's docs say only that the Linea team maintains these components. Linea's risk disclosures say the council has nine members, while the Security Council charter in the Lineth repository says twelve members sign the 5-of-9 multisigs.
- CPU, RAM and bandwidth requirements for a Linea node are not published on the node guides reviewed, and the disk figures date from November 2025.
- Maru's configuration reference marks an Ethereum endpoint as required inside its Linea section, but Linea's canonical mainnet configuration leaves that section commented out for follower nodes; the profile follows the canonical configuration.
- When forced transactions will go live, and their inclusion deadline, are not published; the July 2026 rollup contract upgrade only staged them.
- Linea's network overview says withdrawals are instant and free, which conflicts with its bridge guide (2 to 12 hours and a manual claim on Ethereum); this profile follows the bridge guide.
- Withdrawal rate limits come from the April 2026 Security Council entries and L2BEAT; later changes would appear only in the council record, and the risk disclosures give no figure.
- Who runs the Ethereum validators for Yield Boost staking is not named in Linea's Yield Boost pages, and the amount of bridge ETH actually staked was not measured; the council record gives only the allowance.
- Ledger Wallet's current code keeps Linea behind a feature switch that is off by default; Ledger's remote switch setting, its Linea coin page (404) and its support article (did not render) could not confirm whether users have it. Ledger's status page lists a Ledger-run Linea node, which does not count as wallet support under the custody rule.
- Trezor's Linea page names Trezor Suite, but Suite's public network configuration has no Linea chain; the page may describe the LINEA token on Ethereum. Older Trezor models were not reviewed.
- Community explorers (Lineaplorer, OKLink, Linea for Humans) and third-party bridges beyond the LI.FI aggregator named in Linea's guide were not opened.
- DEX liquidity and activity were not measured; lending markets and venues other than Etherex and SyncSwap were not sampled.
- Atomic swaps, reversible-transfer or account-recovery products, channels, algorithmic stablecoins and networks settling to Linea were not reviewed.
- Linea's RISC-V prover (in development and not yet used in any deployment, per its docs) and its target of hard finality under 30 minutes (Beta v5.4, targeted for the fourth quarter of 2026) were not live at review time.
- The date LINEA joined the burn is unclear: the tokenomics page dates burns from 11 September 2025, while the release notes say Beta v4.2 (5 November 2025) updated the burn to include LINEA.
- The gap between blocks varies: Linea calls about one second its block time, but its node guide says blocks are produced only when transactions are pending; no average interval was sourced.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Linea Mainnet (external site)
- Connect (external site)
- Architecture (external site)
- Maru (external site)
- Run a Linea node (external site)
- Besu (external site)
- Linea Besu (external site)
- Prover (external site)
- Trusted setup (external site)
- EVM state manager (external site)
- State recovery (external site)
- Ethereum differences (external site)
- EIP-7702 support (external site)
- Transaction finality (external site)
- Tokenomics (external site)
- Forced transactions (external site)
- Risk disclosures (external site)
- Release notes (external site)
- Linea Security Council transaction record (external site)
- Canonical message service (external site)
- Canonical token bridge (external site)
- Bridge tokens to Linea (external site)
- Yield Boost risk disclosures (external site)
- Block explorers (external site)
- Linea (external site)
- Linea Mainnet (ETH) Blockchain Explorer (external site)
- Linea blockchain explorer (external site)
- Etherex documentation (external site)
- Contract addresses (external site)
- Smart Contracts (external site)
- USDC Contract Addresses (external site)
- Introducing MetaMask USD (external site)
- Safe & secure Linea wallet (external site)
- Trezor Suite Ethereum network configuration (networkConfig.ts, develop branch) (external site)
- Maru configuration reference (external site)
- Linea Mainnet Maru configuration (docs/getting-started/linea-mainnet/maru/maru-config.toml) (external site)
- Maru Linea Mainnet genesis configuration (linea-mainnet-genesis.json) (external site)
- Ledger Wallet coin-module loaders (loaders.ts, develop branch) (external site)
- Ledger Wallet feature switch currencyLinea (develop branch) (external site)
- Ledger feature-flag definitions (define.ts): a switch declared with no value is off by default (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding