Proof of concept implementations for IPTF.
Warning: These are research prototypes, not production-ready code. Do not use in production without thorough security audits.
pocs/
[project-name]/ # Self-contained PoC
REQUIREMENTS.md # Actionable requirements from use case + approach
SPEC.md # Protocol specification (main deliverable)
README.md # Build/run instructions, limitations
[approach-1]/ # For multi-approach PoCs
SPEC.md
README.md
[approach-2]/
...
libs/
[library-name]/ # Standalone libraries
docs/
CONTRIBUTING.md # PR guidelines
CHANGELOG.md # Repository-wide change history
Each PoC is independent—own language and tooling. No shared dependencies between projects.
| Name | Privacy Primitive | Approaches | Status | Writeup |
|---|---|---|---|---|
| private-payment | Confidential stablecoin transfers | Shielded Pool (Noir), Plasma (Intmax2), Resilient Disbursement Rails | Complete | Shielded Pool, Plasma |
| private-bond | Confidential bond transfers | Custom UTXO (Noir), Privacy L2 (Aztec), FHE (Zama) | Complete | Part 1 — Custom UTXO, Part 2 — Aztec, Part 3 — FHE |
| private-trade-settlement | Confidential atomic DvP | TEE Swap | Complete | Part 1, Part 2 |
| private-identity | Anonymous credentials | Resilient (vOPRF) | Complete | Resilient Plural Identity |
| diy-validium | Confidential institutional payments | Validium (RISC Zero) | Complete | DIY Validium |
| Name | Description |
|---|---|
| binius-mayo | Binius64 zk-circuit proving a MAYO-2 post-quantum signature verifies under a hidden public key |
See docs/CONTRIBUTING.md for PR guidelines. Use pocs/_template when adding new PoCs.
- iptf.ethereum.org — Writeups and documentation
- iptf-map — Mapping of privacy primitives