> For the complete documentation index, see [llms.txt](https://solvency.gitbook.io/picoin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solvency.gitbook.io/picoin/core-concepts/proof-of-pi.md).

# Proof of Pi

Proof of Pi is Picoin’s core consensus computation model.

Instead of brute-force hashing, miners calculate deterministic finite ranges of the mathematical constant π.

The network assigns tasks containing:

* start position;
* end position;
* algorithm version;
* validation parameters.

Miners compute the assigned range and produce:

* result hash;
* Merkle root;
* sample proofs.

The network then validates the work through:

* commit-reveal;
* validator approvals;
* retroactive audits.

Picoin currently uses BBP hexadecimal computation because the BBP algorithm allows direct computation of distant hexadecimal digits without calculating all previous digits.

This makes Proof of Pi significantly more practical for distributed verification.


---

# 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://solvency.gitbook.io/picoin/core-concepts/proof-of-pi.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.