A blockchain's own consensus and settlement layer. The label describes where that protocol processes and orders transactions; security, finality, data availability, and scaling guarantees differ by chain and design.
Supports: Explains Ethereum's protocol-defined finality and the conditions under which blocks become finalized.
Supports: Explains how rollups execute away from L1 while publishing validity proofs and data, with design-dependent trade-offs.
Supports: Explains cumulative proof-of-work assurance and why the cost to alter transaction history grows with subsequent blocks.
Layer 1 denotes a protocol's own consensus and settlement system, not a universal security guarantee
Finality and confirmation assurance vary by protocol and operating conditions
Layer 2 security and exits depend on its contracts, data model, sequencers, bridges, and implementation
Review protocol-specific documentation, custody, and operational assumptions before transferring funds
Before bridging funds to an L2, a user reads that L2's withdrawal and data-availability documentation, checks the L1 contract and supported wallet route, and distinguishes a posted commitment from an immediately withdrawable balance. They do not assume the L1 label answers those questions.
A protocol-defined state in which reversing a block requires violating that network's consensus assumptions and incurring its specified cost. It differs from a wallet confirmation, sequencer response, or settlement on another chain.
The protocols, incentives, and rules that let distributed network participants select and validate a shared ledger state despite delays, faults, or conflicting proposals.
A protocol layer that executes transactions outside an L1 while using that L1 for some combination of data availability, proofs, dispute resolution, or settlement. Fees, finality, bridges, and withdrawal paths depend on the specific L2 design.
Software connected to a blockchain network that can relay data and, depending on its operating mode, validate blocks and transactions under that network's rules. Node capabilities, data retained, privacy, and trust assumptions vary by implementation.
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles