Glossary · Scaling

Layer 2

Published 22 May 2025 · Updated 9 Nov 2026 · 16 min read

Layer 2 (L2) is a separate network that processes transactions away from a base blockchain while relying on it to protect users' funds. Designs publish data or signed commitments so Ethereum or Bitcoin can check results or settle disputes. Each design makes different demands on users and operators.

  • A layer 2 should let users recover assets on the base chain without the operator's permission.
  • Rollups publish data on the base chain, while sidechains use their own consensus and are not L2s.
  • Layer 2 adds capacity, but withdrawals still wait for proofs or challenge periods on the base chain.

What layer 2 means

A blockchain has limited room because every node must check its work. Layer 2s move execution elsewhere while keeping a claim on that chain's security. The base network, such as the Ethereum blockchain, anchors settlement rather than doing every calculation. The definitions below show why different sources draw the boundary differently. Some describe blockchains specifically, while others also include payment channels.

SourceDateDefinition, in its own wordsWhat it adds
ethereum.org, What is layer 2?DatePage updated 14 October 2026Definition, in its own words“A layer 2 is a separate blockchain that extends Ethereum and inherits the security guarantees of Ethereum.”What it addsSecurity inherited from the base chain
L2BEAT, now ETHBEAT, glossaryDateRead 9 November 2026Definition, in its own words“A blockchain that inherits consensus and data availability from another blockchain called L1”What it addsIts definition of a rollup, the strong kind of layer 2
Vitalik Buterin, Different types of layer 2sDate31 October 2023Definition, in its own words“what level of guarantee do you have that you will be able to take the asset back to the L1?”What it addsThe test is getting your assets back
Joseph Poon and Thaddeus Dryja, Lightning white paperDate14 January 2016Definition, in its own words“transactions are sent over a network of micropayment channels (a.k.a. payment channels or transaction channels) whose transfer of value occurs off-blockchain.”What it addsPayment channels on Bitcoin
BIS Bulletin No 126, appendix glossaryDate6 July 2026Definition, in its own words“solutions built on the layer 1 network, where most transactions occur off-chain and are only sporadically or periodically reported back to the underlying layer 1 network.”What it addsA BIS staff view that sets sidechains apart
ITU-T X.200 (identical to ISO/IEC 7498-1)Date1994Definition, in its own words“The Data Link Layer detects and possibly corrects errors which may occur in the Physical Layer.”What it addsThe networking meaning: layer 2 of the OSI model

Test where data lives, how results are checked, and whether users can leave without operator permission. With blockchain rollups, data is published on L1, which checks or challenges state. L2BEAT, renamed ETHBEAT on 4 November 2026, calls rollups strong L2s and validiums and optimiums light L2s. The latter keep data elsewhere. Its 19 June 2025 rule requires working proof systems and a data availability bridge. Projects failing either requirement go under "Other".

Sidechain networks use their own consensus and connect to another blockchain through a two-way bridge. Their validators or federation, rather than the original chain's proof rules, can approve an invalid state. Bitcoin Layers sorts systems on the Bitcoin network into bitcoin native systems, sidesystems and alternative chains. Its layer 2 definition requires a unilateral exit through a Bitcoin transaction. Lightning meets it because each participant can close a channel independently. A connection between networks does not itself transfer security guarantees.

In networking, layer 2 means the data link layer of the OSI model, not a blockchain scaling system. ITU-T X.200, identical to ISO/IEC 7498-1, describes this separate meaning. It groups bits into frames and "detects and possibly corrects" errors from the physical layer. Devices use a 48-bit MAC address on a local network. Ethernet follows IEEE 802.3, and a layer 2 switch forwards frames using the destination MAC address.

How a rollup transaction travels

A deposit, a confirmation and a withdrawal are different events. Follow a rollup transaction through six steps to see which party acts at each point. Most rollups run one sequencer in November 2026. Separate its acknowledgment from the checks that make the result enforceable.

Number 1

Deposit

Users deposit through the canonical bridge, whose base chain contract checks proofs. Third-party bridges add trust in their own signers rather than just the rollup's verification rules.

Number 2

Send

A sequencer orders transactions. Forced inclusion offers a route through L1 if it ignores them. In November 2026, delays reach one day on Arbitrum One and seven days on Scroll.

Number 3

Execute

The rollup executes transactions away from Ethereum. A fast confirmation is the sequencer's promise, not final settlement. The base chain has not yet accepted that result.

Number 4

Publish

Dencun introduced EIP-4844 blobs for transaction data in March 2024. Each holds 131,072 bytes for about 18 days. PeerDAS, introduced in December 2025, lets nodes check availability by sampling.

Number 5

Prove or challenge

An optimistic rollup design accepts state unless a fraud proof succeeds during its challenge period. Arbitrum One allows 6 days 8 hours in November 2026. A ZK rollup requires a validity proof with each state update.

Number 6

Withdraw

Withdrawals follow the challenge period or verified proof. An escape hatch enables an independent exit through L1. The exit window is the time users have to leave before an unwanted upgrade takes effect. Emergency upgrade paths can remove it.

Other scaling designs take different routes. A payment channel normally needs only opening and closing transactions on the base chain. The Plasma design posts commitments rather than full transaction data. If an operator withholds that data, users must exit because they cannot assemble the evidence needed to challenge it. Publishing transaction data on Ethereum addresses that specific problem by making independent checks possible.

How to recognize a layer 2

The figure applies three security tests to eight systems on Ethereum and Bitcoin. Select a system, then compare normal operation with an operator outage. The 9 November 2026 snapshot checks data location, verification and the user's independent route out of an L2.

Figure 1 · Published designs and ETHBEAT's assessment, 9 November 2026Test the security connectionPick a system and switch to an operator outage to see which protections still work without that operator.
System
Scenario
Arbitrum One on EthereumETHBEAT Stage 1Optimistic rollup
Is the data on the base chain?On EthereumTransaction data goes to Ethereum in blobs
Can the base chain check or challenge the state?Fraud proofsAnyone can challenge a state root within 6 days 8 hours
Can users exit without the operator?Yes, after a delayUsers can force transactions through Ethereum after up to a day and propose state themselves
If the operator stopsUsers can self-sequence through Ethereum after up to a day. The exit window is 10 days on the regular upgrade path and none on the emergency path.
Scroll on EthereumETHBEAT Stage 0ZK rollup
Is the data on the base chain?On EthereumTransaction data goes to Ethereum
Can the base chain check or challenge the state?Validity proofsEvery state update needs a proof that Ethereum verifies
Can users exit without the operator?After up to 7 daysUsers can force transactions through Ethereum after up to 7 days
If the operator stopsUsers can force transactions after up to 7 days. Its contracts are instantly upgradable, so there is no exit window before an upgrade.
Lens on EthereumETHBEAT Stage 0Validium
Is the data on the base chain?On AvailTransaction data is posted on Avail, not on Ethereum
Can the base chain check or challenge the state?Validity proofsState updates come with proofs
Can users exit without the operator?NoUsers can only enqueue through Ethereum, and withdrawals freeze if the proposer fails
If the operator stopsWithdrawals are frozen if the proposer fails. Funds can be lost if the data is not available on the external provider.
Celo on EthereumETHBEAT Stage 0Optimium
Is the data on the base chain?On EigenDATransaction data is kept on EigenDA, not on Ethereum
Can the base chain check or challenge the state?Fraud proofsState can be challenged, if the data is available
Can users exit without the operator?NoWithdrawals freeze if the proposer fails, and funds can be lost if outside data is unavailable
If the operator stopsWithdrawals freeze if the proposer fails. Without the EigenDA data, nobody can prove the state, and funds can be lost.
Polygon PoS on EthereumEthereumSidechain, filed under Other by ETHBEAT
Is the data on the base chain?On its own chainSidechains do not post transaction data back to Ethereum
Can the base chain check or challenge the state?No working proof systemState settles on Ethereum if 2/3+1 of validator stake signs, and invalid state roots are permitted
Can users exit without the operator?NoIf proposers fail, users cannot withdraw
If the operator stopsIf its proposers fail, users cannot withdraw. A validator majority, not a proof, decides what Ethereum accepts.
Lightning Network on BitcoinBitcoinState channels
Is the data on the base chain?With the two peersChannel state is not published. Each peer keeps the signed commitments
Can the base chain check or challenge the state?Penalty for old statesBitcoin enforces the latest signed state through revocation keys, if someone watches
Can users exit without the operator?Yes, aloneEither peer can close the channel without the other
If the operator stopsIf the other peer disappears, close the channel alone on Bitcoin and wait out the delay.
Rootstock on BitcoinBitcoinMerge-mined sidechain
Is the data on the base chain?On its own chainBlocks live on Rootstock, merge-mined with over 85% of Bitcoin's hash power
Can the base chain check or challenge the state?No proof for exitsBTC leaves through the PowPeg federation, which signs as 5-of-9
Can users exit without the operator?Through the federationPeg-outs need about 4,000 Rootstock confirmations and the federation's signatures
If the operator stopsPeg-outs depend on the federation's signatures. Users cannot move BTC back to Bitcoin on their own.
Citrea on BitcoinBitcoinCalls itself a ZK rollup on Bitcoin
Is the data on the base chain?On Bitcoin, its own claimCitrea says it uses Bitcoin for data and settlement
Can the base chain check or challenge the state?Validity proofs, BitVM2 bridgeClementine needs one honest participant in each key role, out of N
Can users exit without the operator?Not alone yetA user cannot withdraw to Bitcoin alone today
If the operator stopsPayouts need every signer online or a bonded operator to front the BTC. Independent ratings of Bitcoin systems like this one are thin.

Arbitrum One posts data on Ethereum with fraud proofs. This Stage 1 optimistic rollup allows self-sequencing after up to one day.

Scroll posts data on Ethereum with validity proofs. This Stage 0 rollup allows forced transactions after up to seven days, but no pre-upgrade exit window.

Lens uses validity proofs but posts data on Avail. Withdrawals freeze if its proposer fails, despite the proof system.

Celo uses fraud proofs with data on EigenDA. Withdrawals freeze if its proposer fails, and funds can be lost if that data becomes unavailable.

Polygon PoS validators sign state without a fully functional proof system. ETHBEAT files this sidechain under "Other", and ethereum.org lists it as a sidechain.

Lightning peers keep channel data themselves. Bitcoin enforces the latest signed state if someone watches, and either peer can close alone.

Rootstock secures its own blocks through merged mining. BTC exits depend on its 5-of-9 PowPeg federation, not a user acting alone.

Citrea calls itself a rollup with data on Bitcoin. Its bridge needs one honest participant per key role, and users cannot withdraw alone.

This figure summarizes each system's published design and ETHBEAT's assessment of 9 November 2026.

The Ethereum examples separate three dependencies in the 9 November 2026 assessment. Arbitrum One and Scroll combine published data with working proofs. Lens and Celo keep data elsewhere, creating validium data risks or equivalent optimium risks. A data availability committee or external provider adds trust beyond verification. Withheld data can leave funds frozen or lost. Polygon PoS instead depends on validator approval, so ETHBEAT places this sidechain under "Other" rather than treating it as a rollup.

Exit permissions matter especially for the Bitcoin cases checked on 9 November 2026. Lightning keeps state with peers yet supports unilateral closure. Rootstock is a merge-mined sidechain with a 5-of-9 federation controlling BTC exits. Citrea describes Bitcoin as its data and settlement layer. Its Clementine bridge uses BitVM2 and needs one honest participant in each key role, but users cannot exit alone. Independent risk ratings cover Bitcoin systems far less than ETHBEAT covers Ethereum ones, so the Bitcoin rows rest mostly on each project's own documentation.

How a payment channel works

A blockchain state channel lets two participants update balances without recording every payment on a blockchain. The Lightning Network applies this pattern to Bitcoin. Signed states give either peer a way to enforce the balance independently.

Figure 2 · Lightning specification and client defaultsFollow one Lightning channelStep through seven stages, choose a client, set a routed payment and toggle monitoring to see balances, chain transactions, fees and waits.
Stage
Client
Alice opens a channel to BobWalkthroughAlice 2,000,000 satBob 0 satChannel capacity 2,000,000 sat
What happens
One Bitcoin transaction locks 2,000,000 sat in a 2-of-2 multisig output
Bitcoin transactions so far
1
Routing fee
None
Wait
None
Alice pays Bob 300,000 satWalkthroughAlice 1,700,000 satBob 300,000 satChannel capacity 2,000,000 sat
What happens
Both sign a new commitment and revoke the old one. Nothing goes on chain
Bitcoin transactions so far
1
Routing fee
None
Wait
None
Alice pays Carol 100,000 sat through BobWalkthroughAlice 1,599,999 satBob 400,001 satChannel capacity 2,000,000 sat. Bob forwards 100,000 sat to Carol in his own channel with her
What happens
An HTLC carries the payment across Bob, who earns the routing fee
Bitcoin transactions so far
1
Routing fee
1.1 sat, set by Bob's LND defaults: 1,000 msat plus 1 ppm
Wait
None
Alice and Bob close togetherWalkthroughAlice 1,700,000 satBob 300,000 satChannel capacity 2,000,000 sat
What happens
One transaction pays each side its balance. Neither waits
Bitcoin transactions so far
2
Routing fee
None
Wait
None
Alice closes aloneWalkthroughAlice 1,700,000 satBob 300,000 satChannel capacity 2,000,000 sat
What happens
Alice broadcasts the latest commitment. Bob gets his share at once, Alice waits
Bitcoin transactions so far
2
Routing fee
None
Wait
240 blocks, about 40 hours, with LND defaults
Alice publishes the old opening stateWalkthroughAlice 0 satBob 2,000,000 satChannel capacity 2,000,000 sat
What happens
Bob or his watchtower sees it in time and takes every output with a penalty transaction
Bitcoin transactions so far
3
Routing fee
None
Wait
The penalty must land within Alice's 240-block delay
Alice adds 1,000,000 sat without closingWalkthroughAlice 2,700,000 satBob 300,000 satChannel capacity 3,000,000 sat
What happens
A splice replaces the funding transaction with a new one while the channel stays open
Bitcoin transactions so far
2
Routing fee
None
Wait
No LND release with splicing was found in November 2026

One on-chain funding transaction locks the channel's funds in a 2-of-2 multisig output, which needs both signatures to spend.

The peers sign an updated commitment transaction and revoke the previous one. This payment adds no transaction to Bitcoin.

An HTLC carries the payment through a middle node. The recipient supplies a preimage, and the forwarding node earns its routing fee.

A cooperative close pays both participants through one on-chain transaction. Neither side faces the unilateral close's extra delay.

A unilateral close broadcasts the latest commitment transaction. The closer waits to_self_delay blocks before spending its own output.

Publishing a revoked state allows a penalty transaction taking all the cheater's outputs, if the peer or a watchtower acts in time.

Splicing changes a channel's size without closing it. It was merged into the specification in March 2026, and LND had no splicing release in November 2026.

This walkthrough follows the Lightning specification and each client's default settings checked on 9 November 2026.

With defaults checked on 9 November 2026, each hop charges 1,000 millisatoshi plus a rate per million. Rates are 1 for LND, 10 for Core Lightning and 200 for Eclair's public channels. The calculated cost for a 100,000 sat payment is 1.1, 2 or 21 sat per hop. Force-close delays are 144 blocks, about a day, for Core Lightning, 720 for Eclair and 144 to 2,016 for LND, depending on channel size. Splicing resizes channels without closing them. It was merged into the specification in March 2026.

How much more layer 2s can carry

Capacity depends on what each transaction requires, not just a headline rate. Compare a data-only model with Ethereum's execution ceiling of about 238 plain transfers per second on 9 November 2026. The calculation is not a throughput measurement.

Figure 3 · Page team calculation from published parametersEstimate capacity from dataChange the blob setting and transaction size from 12 to 180 bytes to compare modeled transfers with execution capacity and measured use.
Blobs per block
Bytes per transaction
14 blobs a block, 12 bytes a transactionCalculation12 bytes is an ETH transfer on a rollup (Buterin, 2021).23 bytes is an ERC-20 transfer with ideal compression (Buterin, 2024).100 bytes is the minimum the OP Stack fee model charges for.180 bytes is an ERC-20 transfer in Buterin's 2024 estimate.
Transfers per second12,743data room only, at this setting
Times Ethereum's execution53.5×against about 238 plain transfers a second
Blob data per block1,792 KiB14 blobs of 128 KiB

At Dencun's March 2024 target of three blobs, the model carries 2,731 12-byte transfers per second or 182 180-byte ERC-20-sized transfers.

Pectra doubled the target to six blobs in May 2025, doubling modeled data capacity at the same transaction size.

Since January 2026, 14 blobs per block model 3.6 to 53.5 times L1 execution, using 12 to 180 bytes per transaction.

The November 2026 maximum allows 21 blobs per block for high demand. It is a ceiling, not the target.

These page team calculations use Ethereum's published parameters, Vitalik Buterin's byte estimates and an OP Stack fee floor, not measured throughput.

Blob targets rose from 3 in March 2024 to 14 in January 2026, but layer 2 execution and proving remain separate limits. Blobs carry data, not computation. Blobscan's hourly counts give 7.00 blobs per slot over the 24 hours to 20:00 UTC on 9 November 2026, half the target. ETHBEAT's past-day reading that date shows about 1.04 thousand user operations per second on rollups, about 443 for "Others", and 21.67 for Ethereum. Operation counts do not represent equal work.

How layer 2 families compare

The table separates mechanisms that are often grouped together in scaling discussions. Read across a row to connect data storage, verification and exit rules. The sidechain row is a contrast, not another member of the layer 2 family.

FamilyWhere data goesHow state is checkedHow users exitTypical withdrawalWho can stop or censorExamples
Optimistic rollupWhere data goesOn the base chain, in blobsHow state is checkedFraud proofs within a challenge windowHow users exitWithdraw after the window, or force a transaction through L1Typical withdrawalAbout a week (6 days 8 hours on Arbitrum One)Who can stop or censorThe sequencer can delay, users can go through L1ExamplesArbitrum One
ZK rollupWhere data goesOn the base chain, in blobsHow state is checkedA validity proof with every state updateHow users exitWithdraw once the proof is verifiedTypical withdrawalHours to a dayWho can stop or censorThe sequencer can delay, forced inclusion variesExamplesScroll, ZKsync Era, Starknet
ValidiumWhere data goesOff the base chain, with a committee or a data layerHow state is checkedValidity proofsHow users exitNeeds the data that is kept elsewhereTypical withdrawalLike ZK rollups when data is availableWho can stop or censorWhoever holds the data can freeze fundsExamplesLens (data on Avail)
OptimiumWhere data goesOff the base chain, with a committee or a data layerHow state is checkedFraud proofsHow users exitNeeds the data that is kept elsewhereTypical withdrawalLike optimistic rollups when data is availableWho can stop or censorWhoever holds the data can freeze fundsExamplesCelo (data on EigenDA)
State channelWhere data goesWith the channel's peersHow state is checkedSigned states, penalties for old onesHow users exitEither peer closes the channel aloneTypical withdrawalA cooperative close once it confirms, or a delay of about a day or moreWho can stop or censorA peer can go offline, someone must watchExamplesLightning Network
PlasmaWhere data goesOnly commitments on the base chainHow state is checkedFraud proofs that need the operator's dataHow users exitUsers exit if the operator withholds dataTypical withdrawalA challenge period, mass exits if data is withheldWho can stop or censorThe operator can withhold dataExamplesPlasma designs of 2017 and later
Sidechain (for contrast)Where data goesOn its own chainHow state is checkedIts own consensus, no proof checked by the base chainHow users exitThrough a bridge its validators or federation runTypical withdrawalSet by the bridgeWho can stop or censorThe validators or federationExamplesPolygon PoS, Rootstock

Data availability determines which parties users must trust to reconstruct balances. A proof system determines whether an operator can settle an invalid state. Understanding validity proofs also helps distinguish correctness from privacy. In November 2026, ZK withdrawals can take hours to a day, while optimistic withdrawals take roughly a week. These waits concern exits, not the speed of a sequencer's acknowledgment. Compare the complete path rather than one confirmation number.

How layer 2s developed

Development moved from keeping individual payments off-chain toward publishing enough data for general execution elsewhere. Payment channels and Plasma preceded Ethereum's rollup-centric roadmap. Later changes expanded data capacity and made L2 maturity easier to discuss.

  1. January 2016

    Payment channels become a network

    Joseph Poon and Thaddeus Dryja first circulated the Lightning white paper in 2015 and dated its current draft 14 January 2016. It described payments moving through connected channels, with value transfers occurring off-chain.

  2. August 2017

    Plasma proposes commitment-based scaling

    Poon and Buterin published Plasma on 11 August 2017. Its design posted Merkle roots, leaving users responsible for exiting when an operator withheld the underlying transaction data.

  3. January 2018

    Lightning payments run on mainnet

    Blockstream's store took Lightning payments on Bitcoin mainnet with c-lightning in January 2018. Lightning Labs' lnd 0.4-beta followed on 15 March 2018 as its first mainnet release.

  4. October 2020

    A roadmap centered on rollups

    Buterin presented a rollup-centric roadmap in October 2020. It centered Ethereum scaling on separate execution, while transaction data and settlement remained connected to the original chain.

  5. August 2021

    Arbitrum One opens publicly

    Arbitrum One opened to the public in August 2021. The network used the optimistic approach, which separated execution from the chain responsible for settling challenged results.

  6. June 2023

    Stages describe security maturity

    L2BEAT, now ETHBEAT, introduced Stages in June 2023. The framework added a maturity label, rather than treating the word rollup as a complete description of security.

  7. March 2024

    Dencun adds dedicated data space

    Dencun activated EIP-4844 on 13 March 2024. Blobs gave Ethereum rollups a data publication path that was much cheaper than calldata, with an initial target of three.

  8. December 2025

    Sampling supports higher data targets

    Fusaka introduced PeerDAS on 3 December 2025. A blob-parameter-only fork raised the target to 10 on 9 December 2025, followed by 14 on 7 January 2026.

Where layer 2 protections have limits

Security depends on permissions, available data and someone being able to act. The L2 label does not remove operational dependencies. These limits concern the design and its administration, rather than whether an application feels fast during normal use.

Operators retain upgrade powers

In ETHBEAT's 9 November 2026 snapshot, 22 rollups split into 12 at Stage 0, six at Stage 1 and four at Stage 2. Security councils can retain upgrade powers.

Bridges concentrate trust

The Ronin sidechain bridge lost 173,600 ETH and 25.5 million USDC in March 2022 after five of nine validator keys were taken.

Liquidity becomes fragmented

A BIS bulletin of July 2026 found that liquidity is split across many chains, so the same asset trades in separate pools on each.

Withdrawals still require time

In November 2026, Arbitrum One withdrawals wait 6 days 8 hours. ZK rollup exits wait for verified proofs, taking hours to a day.

Data committees add dependencies

A validium or optimium can verify results yet depend on outside data availability. If a committee withholds data, users can face frozen funds or restricted withdrawals.

Channels need active protection

Lightning requires inbound liquidity for incoming payments and monitoring for revoked states. A peer or watchtower must act within the delay, or cheating can stand.

Building with layer 2 systems

We work on contracts and dApps deployed on layer 2s through our Ethereum development service, ZK rollup projects on established stacks, and custom chains. PixelPlex is a software engineering company founded in 2007 and building in blockchain since 2013. Before deploying on any layer 2, check its forced inclusion delay, its exit window and its Stage.

PixelPlex case icon

We built the Echo protocol as a chain with its own EchoRand consensus and sidechains to Ethereum and Bitcoin through a two-way peg. Its zero-knowledge rollup function executes transactions on Echo and posts validity proofs to layer 1.

  1. Contracts and dApps

    We develop smart contract applications and dApps for deployment on layer 2s. The Ethereum service lists ZK-Rollups and Optimistic Rollups in its tech stack.
  2. Established ZK stacks

    Our ZK rollup development service covers projects on established stacks. These include zkSync Era, Polygon zkEVM, StarkNet and Scroll.
  3. Custom chain builds

    Our blockchain development service covers custom chain development. Its offer includes custom layer 1 and layer 2 builds.
  4. Non-custodial exchange projects

    The DeFi offer of our Ethereum service includes layer 2 non-custodial exchanges, where users keep their own keys.
  5. Reading deployment risks

    Our ZK rollups guide explains Stages and notes that most production rollups sit at Stage 0 or Stage 1 rather than Stage 2.

Discuss your next layer 2 development decision

We can discuss choosing an existing network or building a system around your application's requirements.

Discuss your project

Layer 2 FAQ

What is layer 2 in simple terms?

A layer 2 is a separate network that handles transactions while relying on an underlying blockchain to protect funds. An L2 keeps that connection through enforceable checks or dispute rules. The practical distinction is whether protection comes from those rules or from trusting a separate operator.

Is a sidechain considered a layer 2?

A sidechain is not a layer 2 because its own validators establish consensus instead of inheriting the underlying chain's security. Polygon PoS illustrates the distinction. ETHBEAT lists it under "Other" in its 9 November 2026 assessment because its proof system is not fully functional.

How long does a layer 2 withdrawal take?

A layer 2 withdrawal takes as long as its proof and settlement rules require. In November 2026, Arbitrum One requires 6 days 8 hours, while ZK systems can take hours to a day. A third-party bridge adds its own signer trust, so its transfer should not be confused with the canonical withdrawal path.

How do layer 1 and layer 2 differ?

Layer 1 is the underlying blockchain where settlement rules are enforced. Layer 2 moves transaction work elsewhere while retaining a security connection to it. An L2 can add execution capacity without making the underlying chain settle faster or turning an operator's acknowledgment into final settlement.

Does Bitcoin have its own layer 2s?

Lightning is a payment-channel-based L2 on Bitcoin, with independent closure available to either participant. Other systems using the label can depend on federations or bridge signers. For those systems, the ability to withdraw without cooperation matters more than the name.

Why are fees lower on layer 2s?

On layer 2, batching and compression let transactions share the cost of publishing data, including Ethereum blobs. That can lower the transaction fee burden compared with individual settlement transactions. Fees still depend on demand, and data capacity does not remove execution or proving costs.

What does layer 2 mean in networking?

The networking meaning of layer 2 is the OSI data link layer, which organizes bits into frames and uses local hardware addresses. Ethernet switches use destination MAC addresses for forwarding. This networking meaning concerns communication between devices, not blockchain settlement, tokens or the security of an L2.
Sources (34)

Get updates about blockchain, technologies and our company

We will process the personal data you provide in accordance with our Privacy policy. You can unsubscribe or change your preferences at any time by clicking the link in any email.

Follow us on social networks and don't miss the latest tech news

  • facebook
  • X
  • linkedin
  • instagram
Stay tuned and add value to your feed