Shield.
Bring SOL or supported SPL tokens into Zynull. Your public deposit creates encrypted notes in the protocol.
Your money moves.
Your whole world doesn’t have to follow.
A privacy protocol for SOL and SPL tokens. Create proofs on your device. Keep the details of shielded payments out of public view.
Solana verifies the rules.
Zero knowledge protects the details.
You keep control of your keys.
Bring SOL or supported SPL tokens into Zynull. Your public deposit creates encrypted notes in the protocol.
Your browser creates the proof. The program checks it without publishing the owners, asset or amount of the internal payment.
Recover payments with your private account. Keep funds shielded, send again, or withdraw to a public Solana address.
From a public deposit to a shielded payment. Explore each stage.
A visible deposit creates encrypted notes in the protocol.
Illustrative protocol model. This animation is not live traffic, an anonymity score or a record of actual users. Public withdrawals remain visible.
A public transfer tells a story about your wallet. A shielded payment proves that the transfer is valid while keeping its note owners and value private.
Inside Zynull, a proof replaces public payment details. Deposits and withdrawals still have public addresses and amounts.
Privacy is a property of the protocol.
It deserves more than a black box.
The Solana program verifies Groth16 proofs before updating the shielded state.
Spending keys and private proof inputs stay in your browser. The relayer receives a completed packet.
Public deposits, withdrawals, timing and network metadata remain observable. Independent auditing is pending.
Actual signed operations from the connected Solana test network. Inspect what is public, what is hidden and what each proof verifies.
Connecting to the test ledger. Metrics appear only after proof verification.
Zynull is a privacy protocol on Solana. The app is an interface to that protocol: it creates a private account, encrypts recovery data and generates proofs in your browser.
Internal note owners, assets and payment amounts are protected by the shielded protocol. Deposits and withdrawals expose public accounts and amounts. Timing, relayer activity and network metadata can also reveal information.
Connect Phantom in the Zynull app to approve a public deposit. Send privately and withdraw from your separate Zynull account. A Zynull private address cannot be pasted into Phantom’s standard Send field.
The test release supports Solana devnet and an isolated local ledger with test SOL and TEST tokens. It is a development alpha with a test setup and no independent audit. It is not a mainnet release.
Export the encrypted backup from your private account and keep its password separately. A recovery file and the correct password restore access. Create a fresh backup after adding a private address. The service cannot recover a forgotten password.
Explore the protocol. Try a shielded payment.
See the proof for yourself.
Bugs may cause loss of funds. Start with a small test amount. Check the connected network before sending.
Your assets. Your keys. Your next move.
Connect Phantom, Solflare, Backpack or another Solana wallet.
Your account stays on this device. Start the local test service, then reconnect.
Test alpha · Devnet or local test tokens only. Your encrypted account stays on this device.Self-custody, from your browser.
Protect your keys with a password.
Move test SOL into the protocol.
Send to a Zynull private address.
keys.location localChoose a password to protect your account on this device. No registration needed.
You need both your password and encrypted backup to recover your account on another device.
Available to send inside Zynull.
These funds are inside the protocol, ready for private payments.
Connect your Solana wallet to add devnet funds.
Switch Phantom to Testnet mode and select Solana Devnet. Use only free devnet SOL.
Solana devnet faucet ↗Your confirmed account operations.
Start by adding test funds to your private balance.
This is a public address. Use Receive to share your Zynull private address.
Your password and backup are required for recovery. Zynull cannot restore them for you.
Merge smaller notes for one asset. This uses a private SOL fee and does not withdraw your funds.
Withdraws up to three available notes publicly. It may not withdraw your entire balance.
Internal note owners, amounts and assets are hidden. Public deposits, withdrawals, timing and network metadata remain visible. This test code is not independently audited.
Funds are held by Zynull’s onchain program on Solana. A proof authorizes a payment without revealing the owners of shielded notes or the internal payment amount.
A deposit from a public address is visible onchain. It creates encrypted notes that your wallet can recover.
The recipient opens a private account and shares a private address. The sender’s browser prepares the proof and encrypted delivery.
A relayer receives the completed packet. Spending keys and full private proof inputs never reach the relayer.
Withdrawal addresses and amounts are public. Timing, distinctive amounts and address history can help link entry and exit.
This alpha uses devnet or local test SOL and TEST tokens, according to the connected service. The code is unaudited. The experimental automatic payout route and protection against operator collusion are not integrated.
Actual signed transactions from the connected Solana test network. Compare shielded payments with public deposits and withdrawals.
A valid proof is not an anonymity score. Public timing, fees, relayer accounts and entry/exit patterns remain observable. This evidence comes from the connected test network. It does not measure independent users or real-world anonymity.
Connect the protocol service to load verified transaction evidence.
Evidence is loaded from the public protocol archive. No private account needs to be unlocked.
The browser client uses V9: local proof generation, public history verification, encrypted notes and an encrypted recovery backup.
Every shielded operation must satisfy a Groth16 proof. The client checks the program, verification keys and ledger identity. The test evidence includes signatures, proof checks and the history root.
Connect the protocol servicePROGRAM SHA-256—