New Private SOL transfers with zero traceability

Flush your on-chain trails into a zero-knowledge pool.

ZKnon is a privacy overlay for Solana that routes transfers through a shielded pool. Send SOL to any address without leaving a direct, observable link between sender and recipient — fully verifiable, but privately routed.

Shielded pool model for unlinkable transfers
ZK proofs for deposit & withdrawal correctness
Relayer mode for gasless withdrawals
ZKnon@solana:~/shielded-pool
$ ZKnon create-transfer --asset SOL --amount 0.50

              
Shielded route active
Obfuscating sender → recipient linkage in real time.
ZKnon coin side 1
ZKnon coin side 2
ZKnon main coin
How it works

Three-step shielded transfer pipeline.

ZKnon wraps a normal Solana transfer in a zero-knowledge flow. Deposits enter a shared shielded pool, proofs unlink sender and recipient, and withdrawals exit as clean outputs on-chain.

Step one 01

Deposit into the shielded pool

The sender connects a wallet, selects an amount of SOL, and signs a deposit. Funds are moved into the ZKnon pool and represented as commitments, not balances tied to a public address.

On-chain deposit Commitment + entropy recorded
Step two 02

Prove ownership, not identity

Off-chain circuits generate a zero-knowledge proof that a valid note exists in the pool. The proof reveals nothing about the original address or exact deposit path, only that it is legitimate.

ZK proof Nullifier prevents double-spend
Step three 03

Withdraw to a clean address

A relayer or the user submits the proof, routing SOL from the pool to a fresh recipient address. Observers only see pool → output transfers, with no direct graph link back to the original sender.

Unlinkable output Optional delay & split routing
What is ZKnon?

A shielded overlay for unlinkable SOL transfers.

ZKnon is a zero-knowledge pool that breaks the visible link between sender and recipient. Deposits become commitments, withdrawals emerge as clean outputs, and optional relayers let recipients receive SOL without funding fees first.

ZKnon@solana — overview
$ 
Shielded route ready Type help to list commands.
$ verifying proof … ✔ nullifier recorded — double-spend blocked merkle root updated — pool invariant ok relayer policy enforced (fee cap) withdraw pacing randomized audit mode: spec & circuits in sync
Features

Private transfer hub with a neon core.

Central shielded logic with focused capabilities on both sides — all lines lead into the pool icon in the middle.

DepositsF1

Shielded deposit notes

Convert SOL into commitments using fresh entropy. Public addresses never hold the sensitive balance.

ProofsF2

Zero-knowledge exits

Withdrawals present zk-proofs that spend notes without revealing sender, amount, or prior hops.

ZKnon neon core
RelayerF3

Gasless withdrawals

Optional relayers submit proofs and pay fees, enabling recipients to stay unfunded and unlinkable.

ObfuscationF4

Delay & split routing

Time jitter and split outputs reduce timing correlation and make clustering attacks harder.

Get started

Ready to move in private?

ZKnon makes SOL transfers unlinkable by default. Spin up a clean address flow, route via relayer, and keep your graph invisible. Join the community and start now.

Private by default Fast & low fee Non-custodial
FAQ

Answers to common questions.

Click a card to expand. ZKnon focuses on unlinkable SOL transfers with optional relayer support.

ZKnon is a zero-knowledge overlay for Solana that routes transfers through a shared shielded pool. Deposits become commitments (notes), and withdrawals produce clean outputs that do not link back to the sender.

Deposits are recorded as commitments (hash + entropy). To spend, a proof shows a valid note exists without revealing sender, amount, or path. A nullifier is revealed to prevent double-spend, but it does not reveal the original address.

There is some overhead for proof generation and pool interactions. We optimize proof size and on-chain verification so end-to-end cost remains close to a standard transfer, while delivering strong privacy guarantees.

Relayers submit the withdrawal transaction on behalf of a recipient and take a small fee from the pool output. Recipients can stay unfunded and still receive SOL, further reducing any graph linkage.

ZK receipts can attest that a transfer was valid and funds were controlled by a party, without revealing addresses or amounts. This enables compliance workflows that preserve privacy.

  • Testnet pool + proof circuits hardening
  • Relayer marketplace & fee caps
  • Withdrawal pacing / split strategies
  • Optional ZK receipts for audits
  • Mainnet launch with monitoring & safeguards