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

# Three Proof Types

## Proof Generation Options

Koova offers three ways to generate proof, each with different tradeoffs. The system automatically chooses which proof type to use based on transaction value, merchant reputation, and market conditions. You don’t need to think about it—Koova handles it.

***

### Type 0: Merchant Signature

The merchant signs the offer with their private key. This is the fastest and simplest proof type. It requires trusting the merchant’s key security, but for low-value transactions, this is acceptable.

* **Best for:** Low-value transactions, trusted merchants, speed-critical scenarios.
* **Cost:** Minimal (local computation only)
* **Generation time:** < 1ms
* **Verification time:** < 1ms

***

### Type 1: Notarized Verification

A neutral third party witnesses the transaction and confirms it’s real. This is stronger than Type 0 because it adds an independent witness. It’s slower than Type 0, but for medium-value transactions, the added security is worth it.

* **Best for:** Medium-value transactions, fraud prevention, dispute resolution.
* **Cost:** $0.01-0.05 per proof
* **Generation time:** 100-500ms
* **Verification time:** 10-50ms

***

### Type 2: Zero-Knowledge Proof

Mathematical proof that a transaction is real, without revealing sensitive details. This is the strongest guarantee. It requires no trust—just mathematics. It’s slower to generate than Type 0 and Type 1, but for high-value or privacy-critical scenarios, it’s the right choice.

* **Best for:** High-value transactions, privacy-critical scenarios, maximum assurance.
* **Cost:** $0.10-0.50 per proof
* **Generation time:** 1-5 seconds
* **Verification time:** 100-500ms


---

# 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://koova.gitbook.io/koova-whitepaper/the-platform/three-proof-types.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.