A native Pi payment carries no observable per-unit mining origin on the Pi Mainnet ledger.
“Anyone can create a GitHub repository and claim anything. It could be malware or a phishing script. Official Pi tools are only in Pi Browser. Don’t connect your wallet or enter your passphrase.”
SECURITY.md says the same.SOURCES.md §13–§14, FAQ-DONT-BUY-PI.md.Key idea: “Unofficial” ≠ “scam.” And “official” ≠ “safe” by itself. The real test is what the code actually does — which anyone can read here.
| Property | This repo |
|—|—|
| Wallet connection | ❌ Never |
| Passphrase / seed | ❌ Never |
| Private keys | ❌ Never |
| Transaction signing | ❌ Never |
| Network calls | ✅ Read-only GET to the public API |
| Third-party dependencies | ❌ None (no npm install) |
| Code | ✅ Short, plain Node.js — fully auditable |
Audit it yourself:
Select-String -Path examples/*.mjs -Pattern 'fetch\(' -SimpleMatch # you'll see only read-only GETs
Full detail: SECURITY.md.
| Signal | Safe analysis | Scam | |—|—|—| | Asks for your passphrase / 24 words | ❌ never | ✅ asks | | Asks you to sign an unknown transaction | ❌ never | ✅ asks | | Asks to connect wallet to a random site | ❌ never | ✅ asks | | Ships an obfuscated binary | ❌ no | ✅ yes | | Many dependencies / postinstall scripts | ❌ none here | ✅ often | | Promises profit or “special/ original mined Pi” | ❌ never | ✅ promises | | Only does read-only public API calls | ✅ yes | ❌ no |
The relevant question is never “official or not?” but “what does the code do?” This code: reads public data and prints it. It cannot touch your funds — there is no mechanism in it to do so.
SECURITY.md.Audit, don’t trust — that applies to every repo, including this one.
SECURITY.md · SCOPE.md · SOURCES.md · FAQ-DONT-BUY-PI.md