01 · PRIVATE LAYERProposed
Shield pool
Deposit a standard SOL amount. Your device creates a secret note and publishes only its commitment to the shared tree.
- Input
- Fixed SOL
- You hold
- Private note
- Purpose
- Prove and withdraw
- Public token
- Not required
Solana Mainnet live transaction consoleSOL, under
pSol / Solana privacy infrastructure
SOL, under
your control.
A wallet-controlled foundation for private SOL. Review public transfers today. Inspect the shielded-vault design and follow the treasury funding its development.
Wallet holds every key Simulation before signature Balance refresh after confirmation
Public wallet tools are available. Shielded transfers are not deployed.
pSol / TRANSACTION LAYERSSOLANA
PUBLIC TRANSFER WORKFLOW
PUBLIC WALLET LAYER · IMPLEMENTED
Know what you are signing.
The public transfer tool checks the recipient, amount and estimated network fee, then simulates the transaction before requesting wallet approval.
Open wallet toolsChecking Solana RPC…
Solana RPCConnecting…
Wallet transfersSimulate · sign · confirm
Public tokenNot launched
Privacy vaultNot deployed · audit required
Pump.fun · Solana mainnet
Private Sol (pSol)
Launch on Pump.fun with your own wallet. Once the confirmed pSol mint is configured here, the CA, Pump.fun coin page, and Dexscreener links point to that exact asset.
01
Private Sol · pSol
Review the name, ticker, artwork, quote asset, launch cost, and creator-fee recipient on Pump.fun before signing.
02
pSol / ZEC pair requested
We need the exact ZEC quote mint and Pump.fun eligibility check. A token called ZEC does not establish Zcash backing or redemption.
03
Confirmed addresses
Publish the confirmed pSol CA and pool address. The site does not create a token or add liquidity by itself.
0.1% is the proposed separate LP fee. Pump.fun applies its own current fee schedule. Token trading does not enable the private SOL vault.
What pSol is building
Wallet, market and protocol.
The shielded SOL flow is a protocol proposal. A future pSol market would be separate from the privacy vault. Keeping these systems distinct makes the design easier to evaluate and verify.
02 · PUBLIC LAYERProposed
pSol / ZEC market
The requested ZEC market needs an eligible, identified quote mint and funded pool. Native Zcash ZEC requires a bridge or cross-chain settlement; a Solana token with the same ticker is a different asset.
- Input
- pSol + verified ZEC representation
- You hold
- Public LP position
- LP fee target
- 0.1% · separate pool
- Status
- Quote asset + pool pending
01
→LaunchpSol on Pump.fun; ZEC quote asset pending verification.
02
→LiquidityA separate LP targets a 0.1% swap fee after deployment.
03
Reinforce30% of creator fees is proposed for deeper liquidity.
Four ways through the design
Choose what you want the capital to do.
Proposed mode
Fastest path into the shared shield set
Fixed buckets help deposits look alike. Variable amounts would require a different audited circuit.
- You put in
- A fixed SOL denomination
- You receive
- One private note kept on your device
- What happens
- Prove the note once and withdraw SOL to a chosen recipient
- Fee model
- Shield fee: set only after audit
How it works
Commitments in.
A withdrawal proof out.
Privacy comes from a shared commitment set, not from pSol and not from merely using a fresh address. The note is the one-time credential that links a secret to a valid withdrawal proof.
- 01
Deposit SOL
A fixed denomination enters the future program vault and publishes a secret-derived commitment.
- 02
Keep the note
Your device keeps the secret note. Lose it and the protocol cannot recreate your withdrawal credential.
- 03
Choose a set
Select a published association set whose membership policy fits the proof you need.
- 04
Prove and exit
The proof shows a valid note exists. Its nullifier marks that note spent without publishing which commitment was yours.
Clear boundary.The shielded vault is a protocol proposal. The wallet tools below are real public Solana tools. A future public pSol token and a private vault note would be separate instruments.Read the technical boundary →
Interactive proof model
See what the verifier would learn.
Toggle between the whole illustrative pool and a selected proof set. This is a visualization, not onchain activity.
132 sample commitments
Illustrative data · no deposits or balances
Your deposit In your association set Flagged deposit Outside your set
association set58 of 132 illustrative deposits
flagged inside0 — excluded by this model
proof designmembership ∧ ¬flagged, in zero knowledge
model verdictWould prove exclusion if implemented and audited
Working now
Live wallet console
Review it. Sign it. Verify it.
Connect through Wallet Standard, read a confirmed balance, simulate a transfer, sign inside your wallet, and inspect the confirmed Explorer receipt.
Public by designThese tools do not provide privacy. They prove the wallet and transaction layer works while the shielded protocol remains in development.
Solana Mainnet
Checking wallets…Proposed economics
Creator fees, with a public budget.
Creator-fee sharing requires the actual coin configuration. The fee budget console can allocate native SOL already received, with your wallet approving each transaction.
Buybacks + burns
Creator-fee funds would buy pSol from the market and permanently burn the acquired tokens under public, rate-limited rules.
Pool liquidity
Would fund market depth once the quote asset and pool exist. A separate LP targets a 0.1% swap fee; Pump.fun fees follow its own schedule.
Infra + development
Funds provers, RPC, monitoring, audits, maintenance, and protocol development through a disclosed treasury.
Market liquidity supports public trading. Fees can fund circuits, proving services, and audits; privacy depends on the separately audited shielded vault. Open the 30 / 30 / 40 budget console →
Build status
Protocol development.
The public interface is ahead of the privacy protocol. Every state below is derived from real configuration or plainly marked as pending.
Solana Mainnet wallet layer
Discovery, connection, balance reads, simulation, signing, confirmation, and explorer receipts.
Reference circuits + devnet vault
Commitment and nullifier circuits, test vectors, proof generation, and an onchain verifier.
Audit + trusted setup
Independent review of the circuits and program, plus a public setup ceremony if required.
Public mintNot launched
Pump.funAwaiting pSol CA
Privacy programNot deployed
QUESTIONS & LIMITATIONS
What pSol does today.
- Is pSol private today?
- No. The shielded vault and proof verifier are still a protocol design. The live wallet tools make ordinary public Solana transactions.
- What would make a withdrawal private?
- A valid zero-knowledge proof over a shared commitment set—not a fresh recipient address by itself.
- Does pSol custody keys?
- No. Wallet signing stays inside your wallet, and a future private note must remain client-side.
- Where would LP APY come from?
- A future LP would earn a share of actual pool swap fees. The separate pool targets 0.1%; Pump.fun uses its own fee schedule. APY is unavailable until a funded pool produces real volume.
- Is pSol paired with ZEC now?
- The requested pair is pending. We need the exact ZEC quote mint, its issuer and redemption model, Pump.fun eligibility, and a confirmed funded pool. Native ZEC lives on Zcash; the ticker alone is not enough.
- Does waiting automatically make a note private?
- No. A longer window may allow more eligible commitments to accumulate, but privacy still depends on the implemented proof system, set quality, user behavior, and pool usage.
- Is this a Zcash bridge?
- No. pSol draws from Zcash privacy primitives but does not currently bridge, custody, or wrap ZEC.
- Is the public token the private note?
- No. They are separate instruments. Their minting, backing, redemption, and burn relationship must be specified before launch.
Zcash heritage · Solana execution
Read the design.
Try the wallet tools.
Use the public wallet layer today. Inspect the proposed vault separately from its token and market.