A native Pi payment carries no observable per-unit mining origin on the Pi Mainnet ledger.
This project is an independent technical analysis with read-only tools. It is not affiliated with, endorsed by, or connected to Pi Network / Pi Core Team / SocialChain / PiBit in any way.
Being “unofficial” is normal for a code repository — and it is exactly why you should audit it instead of trusting it. This file tells you how. See also
DISCLAIMER.md.
npm install).Every proof/check script in examples/ performs only read-only HTTP GET requests to the public Pi Mainnet
Horizon API and prints the JSON/messages to your terminal:
const res = await fetch("https://api.mainnet.minepi.com" + path, { headers: { Accept: "application/json" } });
The only exception is
examples/regenerate-snapshots.mjs, a maintenance tool that runs the other scripts and rewrites the localexamples/*-output.txtsnapshots as UTF-8. It makes no network writes, touches no wallet, and writes nothing outside those snapshot files.
Audit it yourself (the code is small, plain Node.js — no libraries):
# Show every network call in the scripts — you'll only see read-only GETs:
Select-String -Path examples/*.mjs -Pattern 'fetch\(' -SimpleMatch
The interactive demo in examples/app-payment-flow/ uses the official Pi SDK and a server-side API key
(PI_API_KEY, read from an environment variable) — it never asks for your passphrase and never signs for you.
Select-String above): read-only GETs only.node examples/….A frequent objection is “Pi is not officially listed and the network is closed, so any fungibility talk is a scam.” That is outdated:
docs/SOURCES.md §13–§14 and
docs/FAQ-DONT-BUY-PI.md.Note: this repo makes no claim about price. It is about asset identity / fungibility only (see
docs/SCOPE.md).
If you believe any script here is unsafe, don’t run it — open an issue describing the exact file and line. Security of readers comes first.