
SECURITY & TRANSPARENCY
Claims you can check.
Limits you should know.
This page describes the running development testnet. It is an operator-authored status report, not an independent security audit or an approved mainnet release.
Transactions and balances are public. Mining uses experimental SHA-256 consensus. Test coins are disposable and have no intended monetary value.
01 / LIVE EVIDENCE
Read what this node reports.
Connecting to testnet node…
- Published v4 genesis hash
1fd55f75486c057e5fb21c1258c6a9c577814d20ebe7ec277820a192615d52ad- Genesis hash reported by this node
—- Genesis comparison
- Awaiting node
- Founder allocation
- —
- Mined after genesis
- —
- Fees burned
- —
- Historical issuance ceiling
- —
- Target block interval
- —
These values come from this site's read-only node and refresh every five seconds. A matching hash is a consistency check against the published genesis, not proof that the operator is honest. Independent validation requires separately built node software and the same pinned genesis.
Inspect raw status JSON ↗Inspect recent blocks JSON ↗Inspect recent transactions JSON ↗
02 / VERIFIED VS. PLANNED
What exists today.
Independent block validation
Two primary Docker nodes have agreed on the v4 genesis and chain tip in operator checks. A separate LAN test node adopted the primary chain at height 1241; reverse-direction block propagation is not yet verified. The public replica provides a read-only explorer. This is a small operator-run lab, not evidence of a decentralized production network.
Fixed height-based subsidy
The testnet schedules 25,000 PNPT per 262,800 blocks across all miners and caps historical issuance at 25 million PNPT including one million at genesis. Calendar-time issuance is not fixed.
Private transactions and RandomX
Sender keys, recipients, amounts and balances are visible in this lab. The current SHA-256 mining rule is not CPU-fair. Confidential transactions and a reviewed CPU-oriented proof of work remain planned. A separate, undeployed core prototype uses panopt: payment URIs and passes 1,280 of 1,280 offline-compatible unit tests with eight exclusions. Its new wallet-cache test covers empty wallets, not migration of populated wallets. That work does not change this lab's privacy or consensus.
Security review and release
No external consensus, cryptographic or wallet audit has approved this code. There is no approved public wallet, miner download or mainnet release. Development source and checklist are currently private.
03 / OPEN RISKS
Problems we have measured.
Difficulty overshoots after miner changes
A deterministic shock model found that v4's two-minute target is unstable when total hash power changes sharply. At 10× hash power, a modeled late 20-block span took 6,132 seconds versus a 2,400-second target; after a 1,000× drop, the first block took 120,000 seconds. These are model results, not forecasts. The rule is unsuitable for mainnet.
Network and wallet hardening remain open
Peer transport is experimental, founder coins are not yet consensus-vested, wallet seeds in the reference CLI are plaintext, and the protocol has not been reviewed for adversarial partitions, timestamps or chain reorganizations.
Public access has limited protection
Confirmed block and transfer lookup now indexes the retained chain. Eight concurrent searches and a bounded API request budget return HTTP 429 when exceeded. The limiter uses forwarded client addresses only from a configured trusted proxy; a two-host public check confirmed separate budgets. Persistent unique-visitor tracking has been removed. Gateway review and representative public load testing remain open.
The development team treats Security and Transparency as requirements to prove, not labels that make unfinished software safe. Last editorial review: 2026-10-22.