Private settlement layer • transparency by proof.
Step 1 — Private Identity
Identity is generated locally and kept in your browser. Do not share your secret.
This secret never leaves your browser. Back up if you want to reuse the same identity.
Cryptographic commitment used inside the backroom.
Helpful when referencing your backroom identity in logs or dashboards.
Group: —
Step 2 — Create Shielded Transfer / Swap
Build a shielded instruction that can be submitted to the Privacy Backroom backend.
Used when the instruction should return unused funds to a separate wallet.
This memo is visible to the backend but not part of the zero-knowledge commitment.
Time window for this instruction before it expires.

Instruction is created using your local identity commitment. Only the commitment and transfer details are intended for the backend — the secret never leaves your browser.

Last instruction
No instruction created yet.
backroom> console ready. generate identity and connect Phantom to begin.
Step 3 — On-Chain Execution
Use Phantom to submit a real Solana transaction that references your shielded instruction.
Funds are sent here from your wallet. Configure this to your on-chain vault.
This is the amount of SOL that will be transferred on-chain.
Attached as a memo so the backend can match this on-chain event with the shielded instruction.

This step sends a real Solana transaction using Phantom. It transfers SOL to your vault and optionally attaches a memo referencing your shielded instruction.