Your Privium account opens with one wallet signature. The browser derives every key the account uses from that signature, shows the account id, and lands nothing on chain; the same wallet opens the same account on any device.
Open your account#
Connect a wallet#
Press Connect wallet at the right end of the nav. The menu, “Connect a Solana wallet”, lists every Solana wallet in the browser; pick one. The order ticket offers the same wallets under “Connect a wallet to trade”, and Account and Receipts list them until a wallet connects. With no wallet installed the menu says “No Solana wallet in this browser.”; on an iPhone it adds an Open in link for each wallet app, which reopens the page inside that wallet’s browser.
Sign the account message#
Press Open account. It sits in the nav, in the order ticket, and on Account and Receipts until the account is open. While the wallet waits for you the button reads Sign in your wallet, and the wallet shows exactly this message:
Text Privium account v1 This signature derives your Privium keys. It moves no funds.It is a message signature, not a transaction: no network fee, no token approval, nothing sent to the chain.
Read your account id#
The nav’s wallet button becomes a drop with your account id, shortened. Its menu shows the Account id beside the Wallet that opened it, with Balances, deposit and exit, Receipts and Disconnect. The Account header reads the id, then “opened by” and the wallet’s address.
From here the app asks the wallet for one thing only: a transaction for each deposit. As the ticket puts it, “Your wallet signs one message to open your account, and once more for each deposit.”
What the signature derives#
Each key is HKDF-SHA256 of the 64-byte signature, with 32 zero bytes of salt and an info label of its own, computed in the browser tab.
| Key | Label | What it does |
|---|---|---|
| Auth key | privium/auth/v1 |
An Ed25519 key that signs every Intent: orders, cancels, Exit requests, Receipt requests and status reads. Its public key is the account’s identity inside every Intent. Because it signs, placing an order never prompts the wallet. |
| Viewing root | privium/view/v1 |
Decrypts your balances and history in the browser. Every Viewing key you hand out derives downward from it, and each Receipt’s pseudonym derives from it and the Receipt’s label. |
| Escape key | privium/escape/v1 |
Makes the proof behind your Escape claim if the Escape ever opens. Its public half is committed in the owner tag of each of your balance leaves, and with the owner salt it opens that tag in an Escape request. |
| Owner salt | privium/salt/v1 |
Blinds those owner tags, so a leaf’s tag says nothing about its owner until the owner opens it in an Escape request. |
| Note key | privium/note/v1 |
An X25519 key pair for the enclave’s replies. Its public half is the reply key that travels inside each deposit note and register Intent, and the enclave seals every reply to it: order results, Exit states, Receipts and the account’s status. The private half opens them in the browser. |
The account id is base58 of SHA-256 over privium/account-id/v1 and the auth public key. It is for display: no API route takes it, and nothing on chain carries it. The enclave learns the account’s public keys from its first Intent, a register Intent sealed like every other, and from the note inside each deposit. Install and connect lists every field the SDK derives.
Where the keys live#
The keys are derived in the tab and held in its memory. Nothing writes them to storage, and no server receives them. A reload, a new tab or Disconnect closes the account; switching the wallet to another address closes it too. Open account then asks for the same signature again and derives the same keys.
The same account on any device#
Ed25519 signatures are deterministic, so one wallet always gives the same signature over the account message, the same keys and the same account id. Open the account on another device with the same wallet and it reads, from the chain and the enclave:
- your balances, decrypted from your current Ledger leaves, and your history, from the Pool’s public Ledger diffs;
- your resting limit orders, in the Open tab on Trade;
- your Exit pieces still on their way, on Account.
The Placed here tab on Trade lists the orders placed from this browser tab, as they seal and fill. The list under “Made from this account” on Receipts is kept in the browser that made each link.
Balances, checked in your browser#
Account leads with Account value, your total in dollars with each asset counted at its mid against USDC, and beside it “Checked against the root of Crossing k”. While leaves decrypt, your balances read “Reading your Ledger”; then each asset shows its amount, its value, what your open orders hold (“n in open orders”), what is on its way out (“n leaving”) and Trade. An empty account reads Nothing here yet. with “Deposit once from your wallet, and every market draws on it, from inside the Pool.” Each balance is read from public data, its Merkle path checked against the root the program stores, and decrypted with your viewing root (Reading your own balances).
History below lists deposits, fills, Exits and fees, decrypted the same way (“Decrypting your entries from the Pool’s public diffs” until they are, and “Reading more Crossings” while older Crossings come in), by Crossing, Entry, Amount (deposits marked +, Exits and fees −), On chain and Time, UTC. Until the first entry it reads “Your deposits, fills, Exits and fees show here as their Crossings commit.” Once there are entries, filters by asset (Every asset or one), period (All time, Last 24 hours, Last 7 days, Last 30 days) and kind (All, Deposits, Fills, Exits, Fees) and a CSV export sit beside the heading.
What lands on chain#
| You | On chain |
|---|---|
| Open the account | Nothing. |
| Deposit | One transfer from your wallet into a Pool vault shard, with a note sealed to the enclave. Deposits |
| Place or cancel orders | Nothing of yours. Each Crossing lands the Pool’s Residual swaps and its Commit. |
| Exit | A payment from a Pool vault to the destination you name. Exits |
| Make a Receipt or a viewing bundle | Nothing. |
Your wallet’s address appears on chain in your deposits and nowhere else. What an observer sees lists what no transaction carries.
When the app answers#
The wallet declined the signature#
The button returns to Open account and nothing is derived; in the ticket and on Account and Receipts the wallet’s message, or “The wallet declined to sign the message.”, shows under it. Press it again and approve the message.
A message under Open account#
Any other failure, such as a wallet that cannot sign messages or a signature that does not verify against the wallet’s key, shows its message under the button and leaves the account closed. Approve the message in a wallet that signs Solana messages.
“The indexer is out of reach”#
Account shows “The indexer is out of reach. These are your balances as of Crossing k.” with Retry. The balances shown are the last ones the browser verified; Retry reads the Ledger again.
The SDK opens the same account from TypeScript with one call, Privium.connect.