# Page Not Found

The URL `bitcoin-native-vs.-bitcoin-l2s` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Bitcoin-Native vs. Bitcoin L2s & Metaprotocols](https://arch-network.gitbook.io/arch-documentation/bitcoin-native-vs.-bitcoin-l2s-and-metaprotocols.md)
- [Why L2s and Meta-protocols Aren’t Enough](https://arch-network.gitbook.io/arch-documentation/bitcoin-native-vs.-bitcoin-l2s-and-metaprotocols/why-l2s-and-meta-protocols-arent-enough.md)
- [The Challenges Facing Bitcoin DeFi](https://arch-network.gitbook.io/arch-documentation/history-of-bitcoin-programmability/the-challenges-facing-bitcoin-defi.md)
- [Example: A Bitcoin DEX](https://arch-network.gitbook.io/arch-documentation/use-cases/using-multi-party-programs-to-enable-amms-lps-and-dexs/example-a-bitcoin-dex.md)
- [Introduction](https://arch-network.gitbook.io/arch-documentation/introduction.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://arch-network.gitbook.io/arch-documentation/bitcoin-native-vs.-bitcoin-l2s-and-metaprotocols.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://arch-network.gitbook.io/arch-documentation/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://arch-network.gitbook.io/arch-documentation/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/arch-documentation/bitcoin-native-vs.-bitcoin-l2s-and-metaprotocols.md`).

You may also use `Accept: text/markdown` header for content negotiation.