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

# Home

> **Prove Everything. Reveal Nothing.**

Welcome to the official ZK-Provenance documentation. This is your complete guide to understanding and using the ZK-Provenance protocol — decentralized document verification powered by Zero-Knowledge proofs on Solana.

## What is ZK-Provenance?

ZK-Provenance is a privacy-preserving document attestation protocol. It lets you **prove the authenticity of any document** without revealing its contents — verified on-chain via Solana in milliseconds.

## Quick Links

| Resource      | Link                                                                       |
| ------------- | -------------------------------------------------------------------------- |
| 🚀 App        | [zkprovenance.app](https://zkprovenance.app)                               |
| 🌐 Website    | [zkprovenance.io](https://zkprovenance.io)                                 |
| 📄 Whitepaper | [zkprovenance.io/whitepaper.html](https://zkprovenance.io/whitepaper.html) |
| 🐦 Twitter    | [@ZkProvenance](https://x.com/ZkProvenance)                                |
| 📧 Contact    | <hello@zkprovenance.io>                                                    |

## Core Stats

| Metric               | Value                           |
| -------------------- | ------------------------------- |
| Proving System       | Groth16                         |
| Elliptic Curve       | BN254                           |
| Hash Function        | Poseidon-128                    |
| Proof Size           | 288 bytes                       |
| Verification Time    | <1ms                            |
| Cost per Attestation | $0.0001                         |
| Network              | Solana Devnet → Mainnet Q4 2026 |

## Documentation Structure

* **Introduction** — What ZK-Provenance is and how it works
* **Quick Start** — Generate your first proof in 5 minutes
* **Core Concepts** — Deep dive into ZK proofs, Poseidon, Merkle trees
* **Compliance Frameworks** — GDPR, HIPAA, SOC2 and more
* **On-Chain Reference** — Anchor program, Program ID, attestation structure


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zkprovenance.io/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.