PROTOCOL / CONCEPTUAL ARCHITECTURE
The privacy model.
Valid transactions.
Fewer exposed details.
ShieldSwap is an interactive prototype of a multi-asset private vault—not a deployed protocol. This architecture describes what real private settlement would require, not technology already running here.
No deployed privacy contracts, proof generation, live liquidity or production audit. Do not send real funds.
01 / THE PROPOSED FLOW
From public assets
to private notes.
Public asset
Chain-specific entry
Private note pool
Proof & nullifier
Transfer or exit
A real deposit would create a commitment to an encrypted note. Spending would prove ownership, note membership and conservation of value. A nullifier would prevent double spending. Exits and public liquidity interactions could still expose metadata.
Notes, not public balances
Encrypted notes can represent ownership without publishing their contents. Secure keys and recovery are essential; neither is implemented by this demo.
Prove validity, not identity
Zero-knowledge proofs can establish that a spend is valid without exposing its secrets. Circuits, verifiers and adapters require independent review.
Every chain has boundaries
Zcash Orchard holds ZEC—not arbitrary BTC, ETH or Solana tokens. Other assets need separate privacy infrastructure and explicit bridging or custody assumptions.
02 / TRUST & EXPOSURE
Privacy is not
invisibility.
Entry and exit amounts, timing, relayers, IP metadata and public DeFi interactions may reveal information. Hiding a balance on-screen provides no on-chain protection.
What works today
A pure in-memory ledger with sample balances, fixed-rate demo swaps, transfers, supply and redemption. Nothing is signed or broadcast.
Before production
Define supported networks and custody. Integrate audited privacy infrastructure, real quotes, confirmation tracking, slippage, refunds and secure key management.