Privacy Today & Tomorrow
The xPrivFi Layer-1 is fully transparent today. A commitment-based privacy layer (CP-Shield v1.0) is under research and will be introduced gradually as a modular, non-disruptive upgrade.
Privacy Today (Current State)
As of today, the XPF Layer-1 blockchain is fully transparent. All balances, transfers, and account states are publicly visible and validated deterministically by every node.
- No shielded balances: all funds are public.
- No commitments: the ledger contains transparent values.
- No nullifiers: standard deterministic double-spend rules apply.
- No ZK proofs: verification is done through traditional validation steps.
This transparency ensures verifiability, predictability and simple auditing for an early-stage chain.
Privacy Tomorrow (CP-Shield v1.0)
xPrivFi is built with a path toward long-term privacy. The planned privacy system — CP-Shield v1.0 — uses a Zcash-style commitment tree, nullifier set and optional zero-knowledge proofs. CP-Shield is designed as a modular Layer-2 privacy layer, not a consensus rewrite.
Planned Components
- Commitment tree: encrypted notes inside a Merkle tree.
- Nullifier set: prevents shielded double-spending without revealing details.
- Shielded transfers: private → private transactions using encrypted notes.
- Transparent ↔ Shielded bridge: opt-in privacy with reversible conversions.
- View keys: optional selective disclosure for audits or compliance.
- ZK proofs (Groth16 / Plonk): cryptographic verification of shielded transactions.
CP-Shield v1.0 will only launch once the circuits, cryptographic assumptions and audits meet strict security standards. No deployment timeline is guaranteed.
Design Philosophy
Privacy in xPrivFi follows three core principles:
- Opt-in privacy: public by default, private when chosen.
- Modular upgrades: no consensus-breaking hardforks.
- Security first: correctness and safety over speed.
These principles allow privacy features to evolve safely without destabilizing the main protocol.
Layer-2 Privacy Tools (Interim)
Before CP-Shield goes live, optional Layer-2 privacy utilities may be released. These tools operate off-chain and never modify L1 consensus. Examples may include:
- commitment-based wrappers,
- temporary shielded pools,
- private payment proofs.
These are auxiliary systems, not part of the core protocol.
Future Interoperability
The privacy layer is designed to remain compatible with future external systems, including optional connections to RootBaseLayer and other proof-based ecosystems. These integrations are modular and optional.
CP-Shield v1.0 and all privacy tools described on this page are not implemented. They represent long-term research and may change significantly as the protocol evolves. No timelines or guarantees are provided.