> 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/developers/quick-start.md).

# Quick Start

Picoin currently operates as an early distributed local testnet.

The project supports:

* Proof of Pi mining;
* validator approvals;
* retroactive audits;
* scientific compute accounting;
* treasury accounting;
* multi-miner testing.

#### Clone the Repository

git clone <https://github.com/devcoffeecoin/PICOIN.git> cd PICOIN/picoin-proof-of-pi

#### Create Virtual Environment

python -m venv .venv

#### Activate Environment

Windows:

..venv\Scripts\activate

Linux/macOS:

source .venv/bin/activate

#### Install Dependencies

pip install -r requirements.txt

#### Run the API

uvicorn app.main:app --reload

***

### &#x20;Running Local Testnet

Picoin includes local multi-miner testing tools.

Example:

python -m picoin testnet continuous --miners 3 --loops 3 --workers 1

This command executes:

* distributed mining simulation;
* validator approvals;
* retroactive audits;
* reward accounting;
* chain validation.

***

### &#x20;Mining Commands

Picoin currently supports local mining execution.

Example:

python -m picoin mine once

Continuous mining:

python -m picoin mine continuous

The mining workflow includes:

* task assignment;
* deterministic computation;
* commit-reveal;
* validator approvals;
* retroactive audits.

***

### &#x20;Science Commands

Picoin includes a Science Compute accounting layer.

Examples:

Stake for Science Compute Access:

python -m picoin science stake --amount 31416

Create Scientific Job:

python -m picoin science create-job --type ai\_inference --metadata-hash HASH --storage-pointer POINTER

View Science Jobs:

python -m picoin science jobs

Check Science Reserve:

python -m picoin reserve status

***

### &#x20;Treasury Commands

Picoin includes a Scientific Development Treasury.

Examples:

Treasury Status:

python -m picoin treasury status

Treasury Claim:

python -m picoin treasury claim

The treasury currently uses:

* timelocked accounting;
* governance-ready structure;
* future multisig support.

***

### &#x20;Health Checks

Picoin includes integrated protocol health checks.

Health checks validate:

* blockchain integrity;
* reward accounting;
* validator availability;
* reserve consistency;
* balance consistency;
* database state.

***

### &#x20;Docker Testnet

Future versions of Picoin are expected to support distributed Docker-based testnets.

Planned configurations include:

* bootstrap node;
* miner nodes;
* validator nodes;
* auditor nodes;
* distributed networking.

***

### &#x20;Running Multiple Nodes

Picoin is evolving toward distributed multi-node operation.

Future distributed testnet versions are expected to support:

* peer discovery;
* node synchronization;
* distributed validation;
* gossip propagation;
* distributed consensus.


---

# 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/developers/quick-start.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.