Wallet & identity
Local keys · client-side identity
No keys stored on server
Wallet dock
Step 0
Connect wallets that will sign Solana deposits and EVM withdrawals.
Solana wallet
Not connected
—
Phantom
EVM wallet
Not connected
—
MetaMask
Private identity
Step 1
Identity is local. zkChan only uses commitment hashes for proofs.
Secret (Base58)
Not generated
Commitment
Pending
—
Shield key
Public key
Derived from secret
—
zk identity
Shielded bridge
Fund shielded pool on Solana and release on destination chain.
zk-SNARK proof · no traceable link between sides
Shielded cross-chain bridge
Deposit SOL into a shielded pool and redeem privately on another chain.
Step 2 Shielded transfer / swap
zk proof · relayed off-chain
From chain
Source
To chain
Destination
From token
Shielded deposit
To token
Redeem asset
Amount
Balance: 0 SOL
Slippage tolerance
Advanced
Receiver wallet (destination chain)
Refund wallet (optional)
Deposits are shielded on Solana. Redeem proofs are verified before release.
Estimated bridge fee: —
Ready in local mode · no live RPC
Control & telemetry
Debug, copy state, follow the proof flow.
Local log only
No activity yet. Connect a wallet or create a shielded instruction to begin.