Layer 1

Overview

Layer 1 refers to the foundational blockchain that validates transactions and maintains its own canonical ledger through a native consensus mechanism. Bitcoin, Ethereum, and Solana are examples, although their execution and data models differ substantially.

The base layer defines block production, finality, fees, state availability, and the native asset used for protocol operations. Higher layers may execute activity elsewhere but ultimately rely on some Layer 1 property for settlement, data, or dispute resolution. Applications should verify the exact network, chain identifier, address rules, native fee asset, and confirmation model. The label does not imply superior decentralization or scalability. Payment processors must base crediting and reorganization controls on the particular chain’s security and finality rather than generic Layer 1 assumptions. Payment policy for Layer 1 needs the exact stage that authorizes fulfillment, together with reorganization and upgrade handling. Users should be told whether a status represents local acceptance, shared-security confirmation, or final settlement on another layer.

Sharing security or infrastructure with another layer does not make those stages identical or eliminate application-specific risk. Layer 1 should be described by the execution, consensus, data-availability, messaging, and settlement responsibilities it performs. Integration with Layer 1 should identify all connected networks, native and represented assets, message routes, fee assets, and the points at which upgrades can change behavior. Cross-layer inclusion, execution, and finality may occur at different times. A healthy local endpoint can coexist with delayed cross-layer settlement or unavailable exits. Operational monitoring for Layer 1 should separate local chain progress from the health of relay, settlement, bridge, or data-publication dependencies.