• Reading the docs…
Start trading

Trading

Receipts and viewing bundles

Receipts gives you two ways to show your trading without a wallet attached. A Receipt states results over a span of Crossings, signed by the enclave, and anyone checks it at /r. A viewing bundle opens exactly the part of your history you choose to one reader, who decrypts it at /v. Neither sends a transaction.

Make a Receipt#

  1. Set the span#

    On the Receipt tab, under What it proves, From Crossing and To Crossing bound the Crossings the claims cover, both included. They start at Crossing 1 and the latest committed Crossing.

  2. Choose the claims#

    Each claim is Off, Exact or At least. Realized PnL and Fill count start on Exact, Return on capital and Volume on Off. Exact names the claim and nothing more: the enclave computes the figure from your history and writes it into what it signs. At least opens a field for the threshold, and the Receipt states only that the figure reaches it.

  3. Choose how it is counted#

    Counted in sets the quote asset every value is counted in, USDC or SOL. Cost basis is Average or FIFO.

  4. Name the label#

    Label takes up to 48 characters. “The same label gives the same pseudonym every time, so Receipts under one label build a track record.” A fresh label gives a Receipt that stands alone. The field starts as “receipt”, which is also what it publishes under when left empty.

  5. Read the preview#

    Beside the form a card headed “What the enclave will sign” shows the label, the claims you chose with their thresholds, the span, the Pseudonym “From your viewing key and this label”, the Enclave key “The attested enclave” and the Ledger root “The root of Crossing k” for the To Crossing. An Exact claim reads Exact until the enclave fills in its figure.

  6. Press Make Receipt#

    The button reads The enclave is signing while the request travels. It is an Intent signed by your auth key, so there is no wallet prompt. The enclave replays your history, computes each figure, checks every At least threshold and signs, and the card returns marked “Signed by the enclave” with the exact figures filled in.

The claims#

Claim Exact states At least takes
Realized PnL The PnL in the span, in the quote asset, net of fees A threshold in the quote asset
Return on capital The time-weighted return A threshold in %
Volume The notional traded, crossed and routed alike A threshold in the quote asset
Fill count The number of fills A threshold count

These are the four claims the form offers; the SDK’s receipt request also states fees, ending equity and the assets traded (Claims). The rules each value follows are fixed in the measured enclave code (How results are computed).

Share it#

The signed card shows each claim with its figure, PnL and volume to two decimals of the quote asset and the return as a percentage, then the Span, the Pseudonym (ψ with the first and last four hex characters), the Enclave key and the Ledger root at its Crossing. Under it, “Anyone with this link checks it in their browser against the chain. The Receipt travels after the #, so the link is the Receipt.” Copy link copies the link (the button turns to Copied), Post to X opens a post with “label on Privium” and the link, and Make another returns to the form. Everything after the # stays in the reader’s browser and never reaches a server. The Receipt names its pseudonym, never your wallet or account.

Every Receipt and viewing bundle you make is listed under Made from this account, on this device, with its label, its time and Open. Bundles are listed by scope: “Whole account”, “asset, all time”, “asset, Crossings a–b” or “One entry”.

Make a viewing bundle#

  1. Choose the scope#

    Switch to the Viewing bundle tab and, under What it opens, pick Account, Asset, Period or One entry. It starts on Asset.

  2. Fill in the scope#

    Asset and Period take an Asset; Period adds From Crossing and To Crossing; One entry takes the Entry from your history, listed as “Crossing k · kind”. The card beside the form, headed Viewing bundle, names the scope and says what the bundle opens.

  3. Press Make the viewing bundle#

    The browser derives the keys that cover exactly that scope from your viewing root and builds the link. Nothing is sent anywhere.

  4. Hand it over#

    The card shows a QR code of the link, and the link sits under it with Copy link and Make another. The bundle travels after the # of /v#, so whoever opens the link reads it in their own browser.

Scope The card’s title What the card says it opens
Account “Whole account” “Every entry of every asset, past and future.”
Asset “asset, all time” “Every asset entry, past and future.”
Period “asset, Crossings a to b” “The asset entries between these two Crossings, and nothing else.”
One entry “One entry” “This one entry, and nothing else.”

A bundle opens entries and nothing else: it signs no Intent, moves no token and claims nothing in an Escape (Viewing key).

What a reader sees at /r#

The /r page checks the Receipt in the reader’s browser: its bytes, the enclave key’s Registry entry at the signed slot, the enclave’s signature, and the Ledger root of the span’s last Crossing (Verifying at /r).

State The page shows
Verifying “Checking the signature, the enclave’s Registry entry and the Ledger root”
Verified The card, “Verified in your browser”, with a line naming the Registry slot and the Commit that accepted the root, ending “No wallet is named in it.”
Unknown enclave key “This Receipt does not verify”: “The key that signed it is not one the Pool’s Registry admitted, so nothing here can be taken as the enclave’s word.”
Signature invalid “This Receipt does not verify”: “The bytes in this link were changed after the enclave signed them.”
Root not on chain “This Receipt does not verify”: “It was made against a Ledger root no Commit on chain accepted.”
Malformed “No Receipt in this link”: “A Receipt travels after the # of its link. Ask whoever shared it for the whole link, or make one of your own.”, with Make a Receipt

A failed check also gives its reason in one line under the explanation. A verified page links to Trust, “What the enclave key is”.

What a reader sees at /v#

The /v page reads the Pool’s public Ledger diffs, checks each against the Commit that sealed it, and decrypts the entries the bundle covers (Viewing bundles at /v). Its title names the scope: “The whole account, all time”, “asset, all time”, “asset, Crossings a to b” or “One asset entry at Crossing k”.

State The page shows
Decrypting “Decrypting the entries this bundle covers, in your browser”
Opened “n entries so far, decrypted here from the Pool’s public diffs; reading more Crossings” while it reads, then “n entries, decrypted here from the Pool’s public diffs”, in a table of Crossing, entry, amount, the transaction on chain (“Inside the Pool” for an entry with none of its own, such as a fill or a fee) and time
Out of scope “Nothing in the Pool’s diffs falls inside what this bundle opens.” The page shows the same line when a diff fails its checks.
Malformed “No viewing bundle in this link”: “A bundle travels after the # of its link. Ask whoever shared it for the whole link.”, with Make a viewing bundle

When the app answers#

“Choose at least one claim.”#

Every claim is Off. Set one to Exact or At least.

“Give claim a threshold to prove.”#

An At least claim has no threshold; the message names the claim. Type a value above zero.

“The claim predicate is not satisfied.”#

Your figure for an At least claim falls short of its threshold over the span; the message names the claim (realizedPnl, return, volume or fills). Lower the threshold, set the claim to Exact, or change the span, and press Make Receipt again.

“The sealed Intent is invalid.”#

The enclave refused the request for another reason, as when the To Crossing is past the latest Commit. Change the span and press Make Receipt again.

“The enclave has not signed it yet. It comes back on this page when it does.”#

The request did not reach the enclave, as when intake is unreachable. Press Make Receipt again.

“This entry could not be found in its Crossing’s Ledger diff. Try again once the Crossing reads.”#

A One entry bundle needs the entry’s place in its Crossing’s Ledger diff, and the browser could not read that diff or find the entry in it. Press Make the viewing bundle again.

The SDK makes the same Receipt with receipt, verifies one with receipts.verify, and builds and reads bundles with disclose and readBundle.