Voidify
Community guide

Voidify

Privacy on Solana

Public ledgers expose transfers between wallets. A shared pool and zero-knowledge proofs make it harder to match a Voidify withdrawal to its original deposit.

Open protocol interface ↗𝕏 @VoidifyPrivacy ↗ Telegram data bot ↗
+∅ / Privacy pool
Decentralization

Who does what in Voidify?

Users hold the withdrawal secret
The user creates a proof on their device. The Solana program checks the proof and whether the credential has already been spent. The site author has no role in approving withdrawals.
Community members run relayers
Members who meet the staking requirements can register a relayer, submit a withdrawal and pay its network fee. A relayer cannot redirect the payment.
Interfaces run independently
The community interface can be distributed through IPFS or run locally. If this site goes offline, the program remains on Solana and can be reached through another compatible interface.
Anyone can check the deployed code
The Nova source is public. Anyone can rebuild it and compare its hash with the program deployed on Solana mainnet.
Who can change the rules?

Community materials describe proposals, voting and delegation. To establish who controls a specific pool, check both its parameter permissions and the program’s upgrade authority. This site has not independently verified every mainnet permission.

How the pool works

01

Deposit

Deposits enter a shared pool. The chain records a cryptographic commitment while the user keeps the secret.

02

Prove

A zero-knowledge proof establishes the right to withdraw without specifying which deposit it came from.

03

Withdraw

Once the proof is accepted, the pool releases funds to the recipient. A nullifier prevents reuse of the same credential.

Voidify Nova · Flexible amounts

  1. Select the asset. Open Nova and check the network, asset and live pool limits. The published SDK lists separate SOL, USDC and VOID pools. A balance in one pool cannot cover a withdrawal from another.
  2. Make a deposit. Enter an amount within the limits. If you use a passphrase, save it privately before signing. Review the amount and program in your wallet, then wait for confirmation.
  3. Recover the balance. Reconnect the same wallet, use the same passphrase if you set one, and let Nova scan for encrypted outputs. A cleared browser cache can require a fresh scan. A serialized Note is a spendable secret.
  4. Withdraw. Choose an amount within your available balance and the pool limits. Verify the recipient’s Solana address, fees and net amount. With a relayer, your device generates the proof and the relayer submits it. The SDK also supports direct submission. Check the transaction signature before retrying.
Read the SDK documentation ↗

Voidify Classic · Fixed denominations

  1. Identify the original pool. Classic follows the fixed-denomination design in the early whitepaper. For an existing Note, identify the network, asset, denomination and original pool from your private records before opening a compatible interface.
  2. For a new deposit, first verify that the specific pool still accepts deposits and has a working withdrawal path. Choose an offered denomination. Save the private Note when generated and check the wallet transaction before signing.
  3. Keep the Note with its pool information. A public deposit signature can confirm the transaction but cannot replace the secret required for withdrawal. Enter the Note only in a verified client compatible with that deployment.
  4. Redeem the Note. Check the recipient and displayed fees, generate the withdrawal proof and wait for confirmation. A successful redemption consumes that Note once. This guide has not verified which Classic pools currently accept new deposits.
Read the whitepaper ↗

Protecting your privacy

  1. Know what remains public. Amounts, timing and wallet activity can still suggest a link. A rare amount in a quiet pool can stand out. Elapsed time alone does not add other deposits to that pool.
  2. Separate public identities. An address already published with your name remains identifiable after it receives a withdrawal. A later transfer between your receiving wallet and a known wallet can also reveal a relationship.
  3. Protect secrets at the point of use. Verify the domain and program before connecting. Keep recovery material in an offline or encrypted backup you control. Avoid screenshots, cloud clipboard history and Telegram messages containing secrets.
  4. Understand the relayer’s role. It can broadcast a withdrawal and cover the network fee. It does not hide information you disclose to a website, RPC service or chat. Use a trusted client and share only the public details needed for a query.
Read the whitepaper ↗

Common questions

What does a mixer do?

Deposits and withdrawals are separate transactions. Several deposits in the pool can be plausible sources for one withdrawal.

What remains visible?

Deposits and withdrawals remain public. Timing and wallet reuse may still give observers clues about the link between them.