> For the complete documentation index, see [llms.txt](https://roborus.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://roborus.gitbook.io/whitepaper/the-roborus-solution/4.3-proof-based-execution.md).

# 4.3 Proof-Based Execution

At the heart of Roborus is the principle of **proof over trust**. Robots don’t just claim they did a job, they **prove it cryptographically**.

* **ZK Proof of Delivery:** A drone can prove it entered a delivery zone without revealing its full GPS path.
* **ZK Proof of Coverage:** A robot can prove it scanned or mapped a target area without disclosing the raw sensor data.
* **ZK Proof of Presence:** A bot can verify it was in a required location at a required time without exposing personal surroundings.

This proof-based approach eliminates the need for intermediaries or human auditors. Clients gain mathematical assurance of completion, while robots maintain privacy.

“No Proof, No Pay” is the fundamental rule. Proofs are the only way to trigger payment, aligning incentives for fairness and reliability.