ozky turns every stablecoin payment into a zero-knowledge proof — amount, sender, and receiver hidden on-chain, yet provable on demand.

Every USDC transfer writes the amount, both parties, and the timing to a ledger anyone can read and correlate forever.

• —Addresses cluster — one linked payment leaks the rest.
• —For payroll and treasury, that exposure is a liability.

Funds live as private notes — Poseidon commitments in an append-only Merkle tree (depth 20). You hold secrets, not ledger entries.

• —No account, no public balance.
• —A view tag lets only you scan and find your notes.

To spend, you prove Merkle membership in zero-knowledge and publish a nullifier — Poseidon(rho, owner_sk).

• —The nullifier kills double-spends without naming the note.
• —Value conserves in-circuit; amounts stay hidden.

Proofs are generated client-side in a native Rust core, then verified by Soroban using Stellar’s BN254 and Poseidon host functions.

• —Proving and scanning run off the UI thread.
• —A native ozky-prover sidecar — no Docker for end users.

Every action is its own UltraHonk circuit, all settling into one atomic pool — no public DEX edge, no bridge.

• —deposit · transfer4 · withdraw · split.
• —shielded swap (x·y=k) · escrow · payment channels.

Each spend also proves approved-set membership — owner_pk ∈ asp_root — so shielded funds stay provably clean.

• —Scoped view keys disclose a slice, never the spending key.
• —You prove what you choose, to whom you choose; revocable.

Three Soroban contracts and nine UltraHonk circuits are deployed and exercised on Stellar testnet — real proofs verified on-chain.

• —transfer4: 13 public inputs, verified on-chain.
• —In-pool swap: 14 PI, value conservation exact.

ozky is testnet-first and unaudited by design — a circuit audit is the hard gate to mainnet. We’re looking for auditors, partners, and early users.