> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/architecture/verifiable-computation.md).

# Verifiable Computation

Every state transition on the Nexus blockchain can be checked with cryptographic proofs rather than trusted. That verifiability is produced by the **Nexus zkVM** — a virtual machine that generates succinct proofs attesting that a computation was executed correctly — together with a distributed proving network that produces and aggregates those proofs.

## Why it matters for the Exchange

The Exchange blockchain settles trades, margin, and liquidations on-chain. Verifiable computation lets anyone confirm that execution followed the rules — order matching, settlement, risk — without trusting the operator. Proof coverage expands incrementally as the network matures; the Nexus zkVM is one of several provers that can attest to mainnet execution.

## Proven at scale

This is not aspirational infrastructure. Nexus has operated proving infrastructure at public testnet scale since December 2024, backed by a distributed prover network and academic-grade specifications.

## Learn more

The Nexus zkVM has its own documentation space covering its architecture, SDK, and full specification:

* [Nexus zkVM documentation](https://docs.nexus.xyz/zkvm/overview/the-nexus-zkvm)


---

# 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://docs.nexus.xyz/architecture/verifiable-computation.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.