This is an invitation: to all builders, investors, and users.

Written by: Kevin Liu, Core Contributor of GOAT Network

It all started with an unplanned coffee chat—ultimately becoming the starting point of a mission. GOAT Network's chief economist Redouane sat down with CIO Eric and CTO Stephen, both staunch believers in Bitcoin. The conversation began with complaints about the confusing use of the term "Layer 2." It seems that everyone now claims to be a Bitcoin Layer 2, but in reality, most projects do not adhere to the core spirit of Bitcoin. They label themselves as "Bitcoin L2" for marketing purposes, while their underlying systems rely on federated multi-signatures, external consensus mechanisms, or highly trusted architectures. This has diluted and misused the term "Bitcoin L2."

Thus, over cup after cup of cold coffee, a mission gradually took shape: we need to define what truly qualifies as a "Bitcoin-native Layer 2" network. They did not want to write a specification limited to technical routes but aimed to establish a principle-based standard—a strict guideline built on Bitcoin's values. This is the starting point of this declaration.

This proposal establishes two levels of standards:

1. Core Must-Haves

Without these conditions, a project cannot claim to be a Bitcoin-native Layer 2.

1. Trustless settlement on the Bitcoin mainnet

A Bitcoin-native L2 must frequently anchor its state to the Bitcoin mainnet—ideally with every block, at least once every few hours.

Settlements must include validity proofs (such as ZK proofs) and state submissions, not just Merkle roots or signatures.

Delayed settlements will severely undermine user security and system trust.

2. Dispute resolution must anchor to the Bitcoin mainnet

In the event of fraud or malicious behavior, users must be able to challenge directly on the Bitcoin mainnet.

There should be no reliance on federated arbitration, MPC, multi-signature committees, or centralized approvals.

Final judgments must be enforced by Bitcoin miners, not off-chain intermediaries.

3. Permissionless forced exit mechanism

Users must be able to unilaterally exit the system at any time.

Even if all Sequencer nodes disappear, the exit channel must remain open.

No custodianship, no approval processes required.

4. Proof-based trust-minimized bridging mechanism

Bridges must be non-custodial and enforceable on Bitcoin through proofs.

Design based on 1-of-n or 0-of-n honest assumptions, completely independent of multi-signatures, federated systems, or human governance.

BTC should never be exposed to third-party trust.

5. Continuous online capability and resilience

L2 networks must remain operational in the event of node failures, censorship, or attacks.

This should be achieved through a decentralized Sequencer architecture.

All roles should have open participation or be easily replaceable, and the system must have self-recovery capabilities.

2. Nice-to-Haves

These features are crucial for scalability and user experience but cannot replace core trustworthiness.

1. Fast and efficient exit mechanism

Standard exit processes should be completed within hours, not days.

In case of disputes, the system should also respond quickly and resolve challenges.

2. Gas mechanism priced in native BTC

Using BTC (rather than bridged ETH or altcoins) as the gas asset enhances trust and ecological consistency.

3. Economic incentives for honest behavior

Roles such as Sequencer, Prover, Challenger, etc., should be rewarded for honest operations.

Cheating should be punished (e.g., staked assets being slashed).

The Ethereum L2 ecosystem has thrived because the community has gradually reached a consensus on the definition of Rollups (such as OP Rollup and ZK Rollup specifications). Similarly, a Bitcoin-native Layer 2 network needs to coalesce around a set of high-integrity common standards.

If a system cannot achieve the following:

• Frequently anchor to the Bitcoin mainnet
• Allow users to challenge fraud on the mainnet
• Operate transparently and minimize trust dependencies

Then it is not a Bitcoin-native Layer 2. It is merely a sidechain masquerading under a new name.

These principles form a set of "living standards"—born from dissatisfaction, refined through collaboration, and driven by the spirit of Bitcoin. Some existing systems are already very close to these standards, such as Lightning, which meets several of them, and ZK Rollup is also making gradual progress. However, this standard does not favor any technical route; it is technology-neutral. As long as your Rollup, channel, or bridge meets this standard, it qualifies; if it does not, no amount of marketing will help.

This is an invitation: to all builders, investors, and users.

Let us together defend the integrity of the term "Bitcoin Layer 2." Establish clear, principled boundaries, and do not disguise centralized systems as L2. Honesty is fundamental; if you are providing a service or a sidechain, please state the truth directly.

As Redouane, Eric, and Stephen realized that day, the future has two paths: one where "Layer 2" becomes an empty brand that any system can easily label; the other is to turn it into a commitment, a badge representing fairness and trust. We choose the latter.

Bitcoin has earned people's trust, and its scaling layer must also be worthy of that trust. Let us define Layer 2 by "truth" rather than "trend," and together build a future that Bitcoin deserves.

Welcome to join this discussion!

This declaration attempts to outline the core principles of "Bitcoin-native Layer 2," but it is still not perfect. Whether you are a developer, researcher, miner, or a Bitcoin enthusiast, your perspective is crucial.

Feel free to leave comments, feedback, or write down your suggestions. Let us work together to set a high standard for Bitcoin-native L2, making it not only secure and robust but also practically usable and scalable.

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。