> For the complete documentation index, see [llms.txt](https://arch-network.gitbook.io/arch-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arch-network.gitbook.io/arch-documentation/fundamentals/introducing-arch/state-transitions-anchored-on-bitcoin.md).

# State Transitions Anchored on Bitcoin

Although state data is only held within the Arch Network, each state transition is anchored with a bitcoin transaction. All transitions and their associated data can be requested from the Arch Network and cryptographically verified. While program results are anchored to Bitcoin via a final transaction that is subject to Bitcoin's block time constraint, the throughput of the Arch Network is not bottlenecked by this same constraint; program execution on Arch is limited only to an Arch validator's hardware capabilities.<br>

The Arch Network maintains real-time state, allowing for Bitcoin transaction chains to be built up within the Bitcoin mempool. Because these unconfirmed Bitcoin transactions are controlled by the Arch Network distributed keys, the network can be confident that double spends will not occur, and that all state transitions will eventually be settled on Bitcoin, providing finality for ultimate security.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://arch-network.gitbook.io/arch-documentation/fundamentals/introducing-arch/state-transitions-anchored-on-bitcoin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.