The Privacy Layer uses a zero-knowledge pool to separate private transaction details from public blockchain settlement. Instead of publishing an ordinary account-to-account payment record, the pool tracks cryptographic commitments, state roots, nullifiers, and proofs. Public asset movement remains visible when value enters or leaves the pool.
This section describes the common ZK pool model. Contract interfaces and supporting infrastructure can differ by network.

​
Architecture flow

​
Main boundaries

​
What the proof establishes

The proof lets the pool verify that a transaction follows its rules without publishing the private inputs used to create it. The pool can then:
  • confirm that the input belongs to an accepted pool state;
  • reject an input whose nullifier was already used;
  • add new commitments and update the pool root;
  • execute a public asset leg when the operation deposits or withdraws value.
Zero-knowledge privacy does not hide every blockchain signal. The contract invocation, state changes, and public deposit or withdrawal legs remain part of public network state.

ZK pool model

Learn how commitments, roots, nullifiers, and proofs work together.

Disclosure policy

Understand how an operation controls field visibility.