> 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/network/nodes/overview.md).

# Overview

A prover is a node in the Compute Network that generates validity proofs using the Nexus zkVM. The Compute Network is live on testnet. Mainnet proof generation will launch alongside NexusCore.

To run a prover on testnet today, see [Proving via CLI](/network/nodes/proving-via-cli.md).

#### What provers will prove

* Exchange execution — order matching, positions, risk, liquidations (NexusCore, 5ms blocks)
* Smart contract execution — EVM transactions (NexusEVM, 1s blocks)

Proof coverage will expand incrementally. Initial scope and rollout schedule will be published before mainnet proof generation begins.

#### Requirements

Hardware, network, and software requirements will be published when benchmarks are finalized. Proof generation is computationally intensive — expect requirements significantly higher than full node minimums.

#### Operational expectations

* **Availability** — must be online and ready to accept proof tasks
* **Task completion** — assigned tasks must be completed within the required time window
* **Monitoring** — operators should monitor performance, disk space, and connectivity
* **Upgrades** — prover software must be kept up to date

Provers that fail to meet these expectations will face slashing. Staking requirements and slashing parameters are not yet finalized.


---

# 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:

```
GET https://docs.nexus.xyz/network/nodes/overview.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.

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.