← Back to pSol

Protocol boundary

Private SOL is the thesis. Here is what exists today.

This build separates the privacy thesis from the public wallet pieces that are actually running on Solana today.

Private Sol on Pump.fun

The token name is Private Sol and the ticker is pSol. The launch is performed on Pump.fun using the owner's wallet. This website deployment does not itself create a coin, fund a pool, or deploy a privacy program. Set the confirmed pSol mint to activate the exact Pump.fun and Dexscreener destinations.

Pump.fun uses its own current trading fee schedule. The 0.1% figure on this site is a target for a separate future LP; it is not a promise about Pump.fun fees.

The proposed pooled flow

  1. Deposit a supported fixed denomination of native SOL into a shared custom vault and publish a secret-derived commitment.
  2. Keep the private note client-side; the note is the withdrawal credential and is not the same thing as a tradable pSol token.
  3. Select a third-party association set whose members exclude flagged deposits.
  4. Choose a recipient and submit a zero-knowledge membership-and-exclusion proof. A new recipient address alone provides no privacy.
  5. Reveal a one-way nullifier so the same deposit cannot be withdrawn twice without identifying the deposit.

The privacy primitive is the pooled note. A public pSol/ZEC liquidity pair is a separate market and cannot unlink deposits from withdrawals.

Proposed ways to participate

  • Standard shield: deposit a fixed SOL denomination, keep the private note, then prove a one-time withdrawal.
  • Time-weighted shield: keep the same type of note behind a minimum maturity window so more eligible commitments may accumulate. Waiting alone never guarantees anonymity.
  • Liquidity LP: the requested pSol/ZEC market needs a verified quote asset and funded pool. A separate future LP targets a 0.1% swap fee; the deployed venue determines actual fees.
  • Hybrid: use a private note and a public LP position in parallel. They remain two transactions and two receipts.

APY is not fixed or guaranteed. It can only be calculated from live fee revenue, pool volume, position range, and TVL after the market exists.

Live in this build

  • Wallet Standard discovery and connection; the wallet keeps all keys.
  • Confirmed RPC telemetry including current slot, block height, epoch, and validator core version.
  • Confirmed native SOL balance reads and faucet requests on devnet.
  • Standard public native SOL transfers through the System Program.
  • Pre-sign asset, amount, fee payer, destination, network, RPC fee, privacy status, and simulation review.
  • Wallet signing, confirmation polling, retryable errors, post-confirmation refresh, and explorer links.
  • A wallet-approved fee budget console for received native SOL, enabled only after its public funding and recipient addresses are configured.

The live transfer is public. It does not provide privacy or use a shielded pSol pool.

Dependencies before a privacy pool can exist

  • A formally specified commitment and nullifier construction.
  • Reference circuits, reproducible test vectors, proving keys, and a verifier practical on Solana.
  • A deployed, upgrade-controlled vault program and explicit rules separating private notes from any public pSol token.
  • Independent audits of the circuits and on-chain program.
  • A trusted-setup ceremony if the proof system requires one.
  • Independent set publishers, versioning rules, availability guarantees, and dispute handling.
  • A recovery path that cannot strand deposits and a funded devnet vault.

Proposed creator-fee policy

  • 30% for transparent, rate-limited pSol buybacks and irreversible burns.
  • 30% for pSol/ZEC market liquidity, accounted separately from privacy-vault reserves.
  • 40% for infrastructure, audits, proving services, and protocol development.

The budget console can distribute received native SOL in one reviewed 30/30/40 transaction once public recipients are configured. It does not claim Pump fees, buy or burn pSol, or add liquidity. Automatic execution still requires verified integrations, limits, monitoring, and governance. A future 0.1% AMM fee is a separate pool parameter, not a privacy guarantee.

Fees can finance circuits, audits and proving infrastructure. The budget split itself does not unlink transactions. Pump.fun also offers native creator-fee sharing; verify the actual coin and recipients before its documented final share update, which revokes further admin changes. Official fee-sharing documentation ↗

Why an AMM is not a privacy vault

A pSol/ZEC pool can provide transparent swaps and price discovery. It cannot issue “fresh” SOL or break transaction links. Privacy requires the separately specified commitment tree, nullifier registry, association-set proof, verifier, solvent vault, and independent audit. This repository does not run operator wallets that churn funds or fabricate anonymity-set activity.

The requested pSol/ZEC pair

Native ZEC is on Zcash. A Solana pair needs an identified quote token and, if it represents native ZEC, a documented issuer, bridge or custody model, reserves, and redemption route. A coin with a ZEC ticker alone does not establish any of these properties.

  • Exact ZEC mint and official issuer or bridge documentation: pending.
  • Pump.fun quote eligibility and quote-token program verification: pending.
  • Confirmed pSol mint, pair address, real liquidity, and wallet-signed transaction receipts: pending.

Pump.fun documents SOL and USDC quotes plus supported custom quotes, including eligible Pump coins. Eligibility must be checked against the exact mint and live program state. See coin creation and custom Pump coin quotes. No ZEC swap, deposit, bridge, or redemption is enabled in this build.

Network separation

The production deployments currently run the public wallet, balance, simulation, and standard SOL transfer flow on mainnet. Devnet remains the test environment. Mainnet configuration does not enable the pSol privacy protocol, token, pool, treasury routing, or bridge; those remain blocked on their explicit dependencies.

Owner handoff checklist

  • Replace the temporary public mainnet RPC with a dedicated production endpoint and monitoring.
  • Commission independent audits before deploying any vault, verifier, mint, treasury controller, or LP integration.
  • Create hardware-backed multisig authorities for program upgrades, treasury operations, and liquidity management.
  • Fund reserves and liquidity only after verifying the deployed program ID, mint, pool, treasury, and authority addresses.
  • Set the relevant public NEXT_PUBLIC_PSOL_* addresses in Vercel and Railway after verification, including the four fee-budget addresses if using that console. Never upload an authority key.