Private Vault
The Private Vault holds your private notes, encrypted in your browser and readable only with keys derived from your wallet. This page covers unlocking it and the page that shows it.
Open Shielded Pool in the app sidebar. The Private Vault card on that page is the vault; the rest of the page shows its notes. "Shielded pool" also names the on-chain side, where your notes' commitments live, so losing the vault does not lose the notes — see Recover Notes.
Unlock the vault
- Connect your wallet.
- Open Shielded Pool. The Private Vault card shows Locked.
- Press Sign and unlock and approve the signature in your wallet. The button reads Waiting for signature… until you do.
- The card shows Unlocked, with your notes and Your Privacy Address.
The signature is off-chain and costs no gas. Your privacy keys are derived from it, so the same account always opens the same vault; there is no password. See Keys & Identity.
Which accounts can unlock
| Wallet | Requirement |
|---|---|
| EVM (MetaMask, Rabby, hardware wallets) | Sign-In With Ethereum for app.orbinum.network, with deterministic signing; the first unlock asks for it twice to check it. Talisman refuses it on another site and MetaMask warns, see Origin binding |
| Substrate sr25519 | sr25519 VRF signing: the Talisman or SubWallet browser extension, not the SubWallet mobile app |
| Substrate ed25519 (Ledger included) | Sign-In With Substrate for app.orbinum.network, with deterministic signing; the first unlock asks for it twice to check it. Talisman refuses it on another site, see Origin binding |
| Solana (Phantom, Talisman 3.13+) | Sign-In With Solana (solana:signIn) for the app's domain; the first unlock asks for it twice to check it. Only wallets that refuse that message on other sites can unlock; other Solana wallets keep the public balance, see Origin binding |
When both an EVM and a Substrate account are connected, the vault belongs to the EVM account. An ed25519 key opens a different vault in a Solana wallet than in a Substrate extension — see One wallet per ed25519 key.
The app caches your unlocked session per account and network, encrypted under a browser key that cannot be exported, so a reload needs no new signature. Lock vault (the lock icon by the status) wipes the keys from memory and drops that cache; the next unlock asks for a signature. Disconnecting the wallet drops the cache on every network.
The page at a glance
| Area | What it shows |
|---|---|
| Your Privacy Address | Your orbpriv3:… address, with Show QR code and Copy privacy address — see Receive Privately |
| Operations | Shield ORB, Unshield ORB and Private Transfer |
| Summary pills | Available Notes, Available Total, Spent Notes and Turnover (the total of spent notes) |
| Notes | Available (N) and Spent (N) lists: Amount, Version, Type (see Note types), Commitment, Created, Created tx, Disclosure Key; spent notes add Spent and Spent tx |
| Note filters | Search commitment or amount, sort by Date or Amount, version, type (one chip per note type), date range |
| More actions (…) | Recover Notes, Export Notes, Import Notes, Import Slip / Proof and Export Viewing Key |
| Action | Page |
|---|---|
| Recover Notes | Recover Notes |
| Export Notes, Import Notes | Export & Import Notes |
| Import Slip / Proof | Payment Slips |
| Export Viewing Key | Export Your Viewing Key |
Note types
The Type column says how each note came to you:
| Type | The note is |
|---|---|
| Shield | A deposit of public ORB into the vault |
| Received | A private payment someone sent you |
| Self-transfer | An output of a private transfer to yourself, such as merging two notes into one |
| Change | What came back to you from a private payment to someone else |
| Unshield change | What came back to you from a withdrawal |
| Stake change | What came back to you from a private stake entry or exit |
| Stake refund | ORB the chain minted back to you for a private entry the pool could not settle |
| Stake payout | ORB the chain minted to you for a private exit |
The app reads the type from the transaction that created the note: if that transaction also spent your notes, the note is a self-transfer, change, unshield change or stake change. Until a scan has read the fee of a self-transfer that left a single note, that note shows as Change. A note the chain minted (shares, a refund or a payout) has no transaction of its own: its Created tx is the entry or exit it answers.
Private staking and share notes
Your ORB notes can be staked in a nomination pool without revealing who you are — see
Private Staking. A private entry spends one ORB note and pays you
share notes of that pool (its sN asset), held in this vault.
- Not ORB. Share notes never count toward your ORB balance: Available Total, the Notes list and the unshield and transfer forms show ORB notes only.
- Where to see them. In Staking → Pools → Your stake → Private stake, a card per pool, where you can also add more or exit; and on each pool's page, under Your private stake.
- Back to ORB. Exit privately on the pool's page, or Exit in Your stake, pays ORB back to the vault as a Stake payout note after the unbonding period, 2 eras (about 2 days). An entry the pool could not settle comes back at once as a Stake refund note.
Keeping notes current
While the vault is unlocked, the app syncs every 2 minutes in the background. The sync keeps the Merkle data your stored notes need, so a spend never tells the node which note you use, and confirms on chain any note a scan found but could not confirm yet. It also receives the share notes Stake refund and Stake payout notes of your private stakes, from the blocks that minted them. It does not look for other new notes; scanning does:
- Sync scans what landed since your last scan. The Unshield and Private Transfer forms offer it: "Notes may be out of date — sync to avoid a failed spend."
- Recover Notes scans the whole pool — see Recover Notes.
A newly found note counts once the chain confirms it, normally during the scan that found it. A note that cannot be confirmed yet shows "N notes are not yet confirmed on chain and not counted in your balance. Sync to confirm." with a Sync button; the background sync confirms it within a couple of minutes too.
Running an operation
After you submit a shield, unshield or transfer, the form closes and a progress bar follows you around the app:
| Phase | Steps shown |
|---|---|
| Prepare | "Checking nullifiers…", "Building Merkle path…", "Building output notes…" |
| Prove | "Generating ZK proof…" |
| Sign | "Confirm in your wallet…" (shield only) or "Submitting…" |
| Confirm | "Waiting for confirmation…" |
You can cancel during Prepare and Prove. One operation runs at a time ("An operation is already in progress").
During a network upgrade the Shielded Pool page shows this notice instead of the vault. Shield, unshield and private transfers pause for a few minutes; notes, balances and history are unaffected.
In this section
| Page | What it covers |
|---|---|
| Receive Privately | Your privacy address and how payments reach you |
| Shield | Moving public ORB into the pool |
| Private Transfer | Paying a privacy address, and merging your own notes |
| Unshield | Withdrawing to a public address |
| Activity | Your public and private history |
| Payment Slips | Handing a recipient the note you sent |
| Recover Notes | Rebuilding the vault from the chain |
| Export & Import Notes | Note backups between your devices |
| Note Disclosure | Proving one note's contents to a third party |
| Export Your Viewing Key | Read-only access to your incoming payments for a backend or accountant |
| Vault FAQ | Common questions |
Related
- Privacy Architecture — what the pool hides and what it does not
- Keys & Identity — how your keys are derived from the signature
- Notes — what a note is
- Transaction Lifecycle — shield, transfer and unshield end to end
- Spend Fees — the fee on transfers and unshields