Zero-knowledge privacy pool (zkSNARKs) for the Paryon (PUSD) stablecoin on BCH Chipnet — the core of nito.cash Private Payments (BCH Blaze 2026 submission).
Status: live on chipnet. The full pool lifecycle — deploy, SHIELD, shielded→shielded TRANSFER, and UNSHIELD — is confirmed on-chain (blocks 328733 / 328740 / 328744).
Latest redeploy (Option B): the DEPLOY+SHIELD and TRANSFER were confirmed in the
same block — 329722 (bd72f1f3… / b0a488db…), with the UNSHIELD confirmed in block 329736 (e90b9a56…).
⚡ Multiple shielded transfers in ONE block. Three chained shielded→shielded
TRANSFERs — each spending the previous transfer's pool output — were confirmed
together in a single block,
329764
(60fe613e… · 7d89f877… · ebc6e4f9…,
each ~36.8 KB, no public value moved). Because a transfer spends the prior transfer's
pool output, many private payments can settle in the same block. (Executed on the latest
Option B redeployment described above — pool aa20a458f7….)
| File | Contents |
|---|---|
CHIPNET.md |
Build record + on-chain demo: deployment, the SHIELD / TRANSFER / UNSHIELD worked examples, verifier patching, trusted setup |
CIRCUIT-DESIGN.md |
The Circom / Groth16 joinsplit circuit (note commitments, nullifiers, Merkle tree) |
COVENANT-DESIGN.md |
The CashScript pool covenant (state machine, action-hash binding) |
GENERALIZED-SHIELDING.md |
Why "one assetCategory" is a deployment choice (not a circuit/contract limit) + the per-asset & multi-asset generalization paths |
The main project README lives at APECSdev/nito.cash.