What is layer 0?

The network layer beneath individual blockchains that lets separate chains share security or pass messages, as in the Cosmos and Polkadot designs.

The term is marketing shorthand rather than a formal category, and projects use it loosely. Compare layer 2, which scales one chain rather than connecting many.

You will see it in project descriptions and in exchange listing copy, usually applied to any protocol whose pitch is that other chains are built on top of it. Because there is no agreed definition, two assets described the same way can work very differently, and the label tells you almost nothing on its own.

How it works

Strip away the branding and there are two distinct architectures that get the name, plus a third that is not really either.

The first is shared security. A central chain runs consensus, and connected chains inherit it rather than recruiting their own validators. Polkadot's design works this way: parachains connect to a relay chain that finalizes their blocks, so a new chain does not need to bootstrap its own validator set. Security is pooled, and the price is that the connected chain accepts the relay chain's rules and its slot allocation.

The second is a messaging standard. Chains keep their own validators and consensus, and a common protocol lets them verify each other's state and pass tokens and messages. The Cosmos ecosystem works this way through the Inter-Blockchain Communication protocol, which uses light client proofs so each chain verifies the other rather than trusting an intermediary. Sovereignty is preserved, and each chain remains responsible for its own security.

The third case is a project calling itself layer 0 because it provides a cross-chain messaging service between existing chains. That is a bridge with extra steps, and the trust assumption is whatever set of parties attests to the messages.

The practical question, for any asset marketed this way, is which of the three it is and what secures the connection.

Example

Illustrative comparison. Chain A connects through shared security: it does not run its own validators, and an attack on it would require attacking the relay chain, which is expensive. Chain B connects through a messaging standard: it runs its own validators, so its security is whatever its own stake is worth, and the messaging protocol only guarantees that messages are verified honestly. Chain C connects through an external attestation service run by a committee. If the committee is compromised, assets bridged through it can be minted without backing. Three chains, one label, three completely different failure modes.

Why it matters when you buy

For a buyer, the label matters mainly as a reminder to look at the actual asset. What is measurable is where it trades and how deeply: the chain pages show throughput RampAtlas measures directly, the liquidity view shows spreads and depth per venue, and the buyability grades show how many exchanges list it where you live.

Related terms

• layer 2: scaling one chain rather than linking many
• bridge: moving assets between separate chains
• cross chain messaging: passing data as well as value
• light client: how chains verify each other cheaply
• validator: who secures a sovereign chain
• modular blockchain: separating consensus, execution, and data

Questions

Is layer 0 an official classification?

No. There is no standards body defining it, and projects apply it to shared security systems, messaging protocols, and bridges alike.

Does a layer 0 make connected chains safer?

Only where security is genuinely shared. A messaging standard leaves each chain responsible for its own validators, and a bridge adds a new trust assumption rather than removing one.

Is this the same as a bridge?

Sometimes it is exactly that. Where the connection relies on an external group attesting to messages, the trust model is a bridge's regardless of the name used.