Loading validated pools
One pipeline.Every step on record.
Public intents are routed through the pools. Shielded intents become commitments, and withdrawals spend nullifiers behind a proof. This is the whole path, as it runs.
Incoming_tx
Tx_queue
- ROUTEPool registry
- SYNCChain indexer
- PROOFVerification path ready
- NULLIFIERDouble-spend guard active
Public + shielded intents
Router
- ROUTERoute discovery activeDAMM / DLMM
Slippage guard
Executor
Route / guard / settle
Nullifier registry
- Registry connectedactive
- Root tracking activeactive
- Spend guard activeactive
- Proof context boundactive
Batch prover
Proof verification pipeline
Robinhood Chain · verifier
- Verifier state
- Tracking chain state
- Proof pipeline
- Monitoring
- Block
- 0
- Root history
- Tracked by indexer
Chain verification state
Every pool.One board.
- Pools
- 0
- DLMM
- 0
- DAMM
- 0
Beyond protocol pools.
All verified reference markets remain discoverable. A market is active on network only when its chain-— token, pool, liquidity, and route have passed independent validation.
0 active · 0 listed
Market chart
—
Validated oracle reports
No market feed is linked to this asset.
Two lanes.Never confused.
A zero-knowledge verifier does not make a public transfer private. So ZKBLAST keeps the lanes apart, labels every action with the lane it runs in, and never puts a privacy mark on a public one.
Public lane
DLMM bins and DAMM pools. Every swap, bin and fee is visible onchain, the way an AMM should be when you want price discovery.
- Concentrate liquidity in price bins
- Dynamic fees on full-range pools
- Route swaps across both pool types
- Claim fees per position
Shielded lane
A vault where a deposit becomes a private note. Withdrawing proves you own an unspent note without pointing at which deposit was yours.
- Notes created in your browser
- Proofs generated locally
- Nullifiers stop double spends
- Encrypted note backup and restore
Liquidity,in bins.
Concentrate liquidity around your chosen price. Each bin holds its own reserves, and the active bin moves as swaps cross the range.
Loading on-chain reserves
How a note moves
- Deposit
- Note
- Proof
- Withdraw
Deposit
Approve the exact amount and deposit into the vault. The vault checks the balance it actually received, then emits the commitment.
Your address, the asset and the amount are public.
What stayspublic.
Privacy claims are only useful when they are exact. This is what each lane exposes today, including everything the shielded vault does not hide.
Asset and denomination
- Public AMM
- Visible
- Shielded
- Visible
Deposit transaction and sender
- Public AMM
- Visible
- Shielded
- Visible
Withdrawal recipient
- Public AMM
- Visible
- Shielded
- Visible
Timing of each transaction
- Public AMM
- Visible
- Shielded
- Visible
Which deposit funded a withdrawal
- Public AMM
- Visible
- Shielded
- Hidden among the anonymity set
Note secret and nonce
- Public AMM
- Not applicable
- Shielded
- Never leaves your device
Vault's aggregate LP position
- Public AMM
- Visible
- Shielded
- Visible
Swap size, route, price impact
- Public AMM
- Visible
- Shielded
- Not offered yet
Shipped in order.Built to last.
- Phase 1Live
Public liquidity
- DLMM bins and DAMM pools
- Swap quotes, slippage, routing
- Positions and fee claims
- Phase 2Live
Proof foundation
- Commitment tree, nullifier registry
- Versioned proof verifier
- Reproducible test vectors
- Phase 3Rolling out
Shielded LP vault
- Allowlisted vault pairs
- Encrypted note backup
- Share-based LP accounting
- Phase 4Next
Shielded swaps
- Private routing through the vault
- MEV and anonymity-set analysis
- Independent security review
- Phase 5Later
Ecosystem
- Integrator SDK
- Analytics API
- Partner pool launches
The contracts.
Small, composable contracts, each with one job. Custody stays non-upgradeable where possible, and every proof is checked onchain against a registered verification key.
- ZKBlastVault.solCustody, deposits, withdrawals, pause controls, asset allowlistCore
- CommitmentTree.solIncremental Merkle tree with bounded root historyCore
- NullifierRegistry.solTracks spent notes so none redeems twiceCore
- VerifierRegistry.solApproved verification keys mapped to circuit versionsProof
- ZKVerifierAdapter.solProof verification with an explicit public-input schemaProof
- ShieldedLPManager.solVault-owned AMM positions and share accountingCore
- ZKBlastRouter.solBest-price routing across DLMM and DAMM poolsPeriphery
- FeeAccounting.solDeterministic fee accounting and claimsPeriphery
Provide.Prove.
Start in the public pools. Move into the shielded vault whenever you need to, and watch every step of your proof run in your browser.