Confidentiality hides what a balance holds; unlinkability hides whose it is. A trader in Privium deposits from one wallet, trades through sealed Intents, and exits to another, and the question this chapter answers is how well an observer can connect the two wallets, or connect either of them to the trades in between. We fix three adversaries, define the public transcript they see, and measure what it says about any one trader with Shannon entropy and min-entropy over the anonymity set. We then bound the three channels through which linkage leaks in any shielded pool (amounts, timing, and flow) and give the countermeasures that close each one: denominations, exit delays and Ring exits. The chapter ends with a formal unlinkability game and the theorem Privium achieves in it: the cryptographic layers leak nothing beyond a stated leakage function, and the statistical bounds of the earlier sections measure exactly what that function reveals.
What the chain shows
Privium’s public surface is small and fixed. Every Intent is encrypted to the Coprocessor’s attested key (Chapter 3 gives the HPKE construction, Chapter 5 the attestation), and Intents reach the enclave through its relay or as opaque blobs posted by a relayer, so no Intent carries a trader’s wallet on chain. The Ledger is a Merkle root over ciphertext leaves (Chapter 4). What remains visible is the movement of tokens across the boundary of the Pool and the net flow per pair.
Definition 8.1 (Leakage function). For an execution of Privium up to Crossing , the leakage is the sequence of:
- Deposits : source wallet , asset , amount , slot .
- Exits : destination address , asset, amount, slot.
- Residuals for every pair with a routed Residual (Chapter 7).
- Commit metadata: the root , the Crossing index, the slot the Commit lands in, the number of live leaves, the set of assets it carries (empty for a heartbeat Commit, Chapter 10), the rewrite pattern (for each asset the Commit carries, the positions it vacates and the positions it fills), and the success or failure of each public instruction.
Commits follow a rewrite discipline built on the leaf of Chapter 4. In every asset a Commit carries, it rewrites the leaves the Crossing changed together with decoys drawn uniformly from the asset’s other live leaves, so that at least leaves of the asset are rewritten (parameter: one aggregated range proof covers 64 leaves at 16.5 bytes per leaf, Chapter 4, and a batch of 64 hides each changed leaf among 63 others). Each Crossing that settles also carries one asset in a fixed rotation over the admitted assets, whether the Crossing changed it or not, so no single carried asset shows that it moved; a heartbeat Commit carries no asset. Every rewritten leaf moves to a fresh uniform position with a fresh owner tag, fresh commitment randomness and fresh ciphertexts. In the Encifher model, on which the Ledger builds, programs hold only handles to ciphertexts [10]; Privium publishes the ciphertexts on Solana itself (Chapter 4). Everything an observer of the chain sees is then computable from plus ciphertexts whose distribution does not depend on plaintext. Theorem 8.9 makes this precise.
The table compares that surface with a trader’s footprint when trading from a wallet.
| Observable | Trading from a wallet | Trading through Privium |
|---|---|---|
| Wallet behind each swap | yes | no swap carries a trader wallet |
| Size and side of each order | yes | only the net Residual per pair per Crossing |
| Balance history | yes | ciphertext leaves under one root |
| Entry and exit of funds | the same wallet | deposit and exit, linked only through |
| Position across tokens | yes | not observable |
Adversary model
We consider three adversaries of increasing reach. All three are computationally bounded in and see every Solana transaction, including every ciphertext the Commits publish.
- Chain observer : passive; sees the full transcript.
- Wallet tracker : additionally holds auxiliary labels on wallets (exchange deposit addresses, known traders) and controls a set of Pool accounts of its own, through which it may deposit, trade and exit freely. Clustering of addresses by co-spending and change heuristics is the standard toolkit of such an adversary [6].
- Timing analyst : additionally exploits slot-level timing of deposits and exits, including the heuristic that a withdrawal close in time to a deposit of matching amount came from it, one of the heuristics Wang et al. used to link deposits to withdrawals in zero-knowledge mixers [5].
The guarantees in this chapter rest on three assumptions, each proved or specified elsewhere: the integrity and confidentiality of the Coprocessor enclave (Chapter 5), an honest threshold of the Council, with fewer than of shares in adversarial hands (Chapter 6), and the IND-CCA2 security of the Intent encryption and the security of the Ledger’s ciphertexts (Chapters 3 and 4). Traders who disclose through a Viewing key or a Receipt disclose by choice (Chapter 11), and the game below excludes those disclosures for its challenge accounts.
The anonymity set and its measures
Definition 8.2 (Anonymity set). For an Exit at slot , the anonymity set is the set of honest accounts that hold a live Ledger leaf at . Write .
Because every pair crosses against the quote asset and balances are encrypted, any live account can fund an Exit in any asset: an account that deposited SOL may exit in USDC after a Crossing, and nothing public says it traded. The set is therefore every live honest account, not only those that deposited the exited asset.
Size alone overstates protection when some members are much more likely than others. Let be the random variable “the owner of ”, and let be the adversary’s posterior.
Definition 8.3 (Entropy measures). The Shannon anonymity of is , with effective set size [1]. The degree of anonymity is [2]. The min-entropy anonymity is , and the average conditional min-entropy over transcripts is
Shannon entropy measures the average uncertainty; min-entropy measures the adversary’s best single guess, and is the right measure for a tracker who acts on one guess. Smith argues for min-entropy on exactly these grounds in quantitative information flow [3].
Lemma 8.1 (Ordering of measures). For every and transcript, , with both equalities if and only if the posterior is uniform on .
Proof. , with equality iff is constant on its support. The upper bound is Gibbs’ inequality against the uniform distribution on , with equality iff is that distribution. Both conditions coincide when the support is all of .
The set as a function of Pool activity
The anonymity set grows with the Pool. Model honest account openings as a stationary process with rate per slot and account lifetimes (slots from first deposit to last exit) with mean .
Proposition 8.2 (Set size). In steady state, .
Proof. The number of live honest accounts is the number of customers in a stationary queueing system with arrival rate and mean sojourn time ; Little’s law gives the time-average number in the system as their product, for any arrival and sojourn distributions with finite means [8].
Two consequences follow. The Pool’s anonymity set is not the number of trades but the number of resident accounts, and an account that stays in Privium as its trading account, the way a client stays at a broker, raises and with it everyone’s set. Second, only honest accounts count: an adversary who opens accounts of its own does not enlarge the set it has to search, because it knows which members are its own. Proposition 8.2 bounds the ceiling; the next sections bound how close the posterior stays to uniform below it.
Linkage channels
A shielded pool leaks through the amounts and times at its boundary and through the aggregate flow it shows inside. We bound each channel in turn.
Amount correlation
An Exit of exactly the amount a unique deposit brought in links the two with near certainty. Kappos et al. showed that matching the values that enter and leave Zcash’s shielded pool links a substantial part of its transactions [4]. The bound we need is a general fact about how much any observation can leak.
Lemma 8.3 (Min-entropy leakage of a finite observation). Let be secret and an observation taking at most values. Then
Proof. . Taking gives (8.2). This is the bound of Smith [3]: leakage is at most the logarithm of the number of distinguishable outputs.
Lemma 8.3 is useless for exact amounts, where is as large as the token’s range, and decisive for denominated ones.
Definition 8.4 (Denominations). For asset with decimals, the denomination unit is base units (parameter: one hundredth of a whole token keeps the sub-unit remainder that stays in the Ledger below any meaningful size), and the denomination set is with (parameter: 24 binary denominations cover a single Exit of up to , about whole tokens). A denominated Exit of amount is executed as the pieces for each set bit of , each piece a separate Exit with its own delay (next section). Deposits through the SDK are split the same way.
Theorem 8.4 (Amount leakage under denominations). Each denominated piece lowers the adversary’s average min-entropy about its owner by at most bits. If deposits are denominated as well, the candidate set for a piece of denomination is the set of honest accounts live at its slot, and no exact-match link exists.
Proof. A piece’s amount takes at most values, so (8.2) with gives the first claim. For the second, a piece of denomination is a sum the Ledger can debit from any account whose encrypted balance covers it, and since deposits arrive in the same denominations, every denomination class contains every honest depositor who used that class; balances after trading are not observable, so the amount does not narrow the set below the live accounts.
The contrast is sharp. With exact amounts, a deposit of 1,234.567 USDC followed by an Exit of 1,234.567 USDC is a fingerprint. With denominations, both are sums of pieces shared by everyone in the same class, and the pieces themselves are scattered in time.
Timing correlation
An Exit soon after a deposit, in a quiet Pool, has few plausible sources. We bound the timing analyst’s success in a continuous-time model with slots as the unit.
Model. Honest deposits in the relevant class (one denomination of one asset, or all deposits if amounts are not denominated) form a stationary Poisson process with rate per slot. Each deposit’s matching Exit occurs after a holding time drawn independently with density bounded by . The adversary sees all deposit slots in the class and the slot of a target Exit, and guesses which deposit it came from.
Theorem 8.5 (Timing bound). The adversary’s success probability is at most
Proof. Condition on a target Exit at . By the Palm property of the Poisson process (Slivnyak’s theorem), the other deposits form a Poisson process of rate independent of the target, whose own deposit lies at with . All deposits being exchangeable a priori, the posterior that deposit is the source is proportional to , so the best guess succeeds with probability
which is at most . Campbell’s theorem gives and . By Chebyshev, . On the complement, . Hence .
The bound depends on the holding-time density only through its peak. A Pool whose traders hold for varied times is already hard to time; the danger is a sharp peak, a trader who always exits a fixed number of slots after depositing. An exit delay flattens every peak.
Corollary 8.6 (Exit delay). If each Exit is executed after an additional delay drawn independently from the exponential distribution with mean slots, then for any trader behavior
Proof. The holding time becomes with independent of , so its density is the convolution , and for any distribution of , including a point mass. Substitute into (8.3); the entropy bound is (8.1) applied to the success probability.
The exponential is the natural choice: its peak density is , and it is memoryless, so an observer who has waited slots since an Exit request learns nothing about the remaining delay. The Coprocessor samples inside the enclave at the moment the Exit request is decrypted, so the schedule is unknown to everyone, the requester included. The recommended mean is slots (parameter): 30 minutes at the slot time of Chapter 9, long enough to cover half an hour of Pool deposits and short enough for a trading account. A trader can request an immediate Exit, which is then bounded by (8.3) with the trader’s own holding-time density.
Denominations and delays compose. With denominated amounts, each piece is timed against deposits of its own denomination only, so in (8.4) becomes the class rate ; the pieces of one Exit are delayed independently, so they arrive interleaved with other accounts’ pieces of other denominations and are not observable as one Exit.
Flow correlation
Inside the Pool the public traces of trading are the Residual, the rewrite pattern and the Crossings’ times. For pair in Crossing , contains the vault deltas of the routed size (Chapter 7), the positions rewritten in each carried asset, and nothing about the crossed size , the number of Intents, or their owners.
Apart from the heartbeat, which carries no asset and settles nothing, a Crossing goes on chain only when it settles something (Chapter 10), so its slot shows that the Pool had work in that batch, and its carried set shows in which assets, alongside the one in rotation. What the work was, a trade, a cancel, a deposit credit, an Exit piece, an expiry or a resting order the market reached, and whose it was, stays sealed: the schedule of Crossings follows the slots at which Intents reached intake, their expiries and limits against the live price, and the boundary events of , and takes no account identity as input.
Proposition 8.7 (Residual and rewrite leakage). Under the rewrite discipline and the confidentiality of the enclave: (a) for every honest account and every Crossing, the adversary’s posterior that had an Intent in pair given is the same for any two honest accounts with identical public deposit and exit records; (b) for any leaf, the adversary’s largest posterior that a given position holds it never increases from one Crossing to the next, and is at most from the first rewrite of the leaf onward.
Proof. (a) The Residual is a deterministic function of the multiset of eligible Intents’ sizes, sides and limits, the mid and the seed (Chapter 7); it does not take account identities as input. The slot and carried set of each Crossing are functions of the times and assets of the work it settles, which carry no account identity either. A rewrite batch is a set of vacated and filled positions with fresh tags and ciphertexts, which carry no plaintext and no account identity under the assumptions of Theorem 8.9. Two honest accounts with identical public records are therefore exchangeable given , so their posteriors coincide. (b) Within a batch of leaves, the leaves are relocated to uniform fresh positions and their new public parts are independent of the old ones (Theorem 4.3), so the map from vacated to filled positions is uniform in the adversary’s view. A filled position therefore receives the average of the posterior mass on the vacated positions, at most , and a position outside the batch keeps its mass. After the leaf is in a batch, its mass is spread over positions, each at most .
A Residual reveals that someone in the Pool traded a net amount in a pair; it never reveals who, and a Crossing in which buyers and sellers cancel leaves no public trace beyond its Commit’s slot and rewrite batches that look like decoys. Every deposit credit is itself a rewrite batch, so from the first Crossing that touches a leaf the rewrite pattern locates it only to within positions. The tracker’s tools that read a wallet’s history and react to its next move [7] have no wallet to read.
Countermeasures in the product
The three countermeasures are defaults in the SDK and the Coprocessor, not settings a trader has to find.
Denominations. The SDK splits deposits and Exits into pieces by Definition 8.4; the sub- remainder stays in the trader’s Ledger balance.
Exit delays. Each piece is scheduled by the enclave with an independent exponential delay of mean , giving (8.4) per denomination class.
Ring exits. An Exit can land in a Helius Ring instead of a wallet. The default Ring encrypts assets and amounts while wallets stay visible; Custom Rings can be configured anonymous, encrypting counterparties and balances, with mainnet release targeted for Q4 2026 [9]. An Exit through a Ring adds a second, independent mixing stage, and the two stages compose.
Lemma 8.8 (Composition). Let a funds path pass from a deposit wallet through a Privium Exit into a Ring and out to a wallet , and let the observations of the two stages be independent given the intermediate Ring deposit . If the best success probability of linking to its Pool Exit is and that of linking a Ring deposit to its Ring withdrawal is , then the probability of linking to is at most .
Proof. Give the adversary, in addition to its view, the identity of ‘s Ring withdrawal. This can only raise its success. Given that, the Ring stage is fully revealed and linking to is exactly linking to , which succeeds with probability at most . Symmetrically, revealing the link from to reduces the task to the Ring stage, bounded by . Each bound holds for the original adversary, which knows less.
The listing shows the SDK’s Exit with the defaults written out, and the denomination split.
export interface ExitOptions {
denominate?: boolean; // default true: split into D_a pieces
delay?: "default" | "none"; // default: enclave samples D ~ Exp(mu) per piece
via?: "wallet" | "ring"; // ring: land in a Helius Ring
}
export function denominate(amount: bigint, unit: bigint, J: number): bigint[] {
let units = amount / unit;
const pieces: bigint[] = [];
for (let j = 0; j < J && units > 0n; j++, units >>= 1n) {
if (units & 1n) pieces.push(unit << BigInt(j));
}
if (units > 0n) throw new Error("amount exceeds largest denomination run; split the Exit");
return pieces;
}
export async function exit(
client: PriviumClient,
asset: PublicKey,
amount: bigint,
to: PublicKey,
opts: ExitOptions = {},
): Promise<ExitTicket> {
const unit = client.denominationUnit(asset);
const pieces = opts.denominate === false ? [amount] : denominate(amount, unit, client.params.J);
const request = {
asset, to, pieces,
delay: opts.delay ?? "default",
via: opts.via ?? "wallet",
nonce: client.nextNonce(),
};
const sealed = await client.sealToCoprocessor(request); // HPKE to the attested key
return client.relay.submit(sealed);
}
The request travels like an Intent: sealed to the Coprocessor and relayed, so neither the destination nor the split is visible until each piece executes. The ticket lets the SDK track pieces as they land.
The unlinkability game
The statistical bounds measure what reveals. What remains is to prove that the rest of Privium’s transcript, every ciphertext, signature and root, reveals nothing more. We state this as an indistinguishability game in which the adversary must tell which of two accounts it chose funded an Exit.
Definition 8.5 (Game ).
- Setup. The challenger runs Privium’s setup: the Coprocessor generates inside the enclave and registers it (Chapter 5); the Council runs key generation (Chapter 6). The adversary receives all public keys and the key shares of any Council members of its choice.
- Oracles. The adversary may open accounts, deposit, submit Intents and request Exits for any account, advance slots (which runs Crossings and Commits), and corrupt any account, receiving its keys and Viewing key. It sees every transaction, every ciphertext the Commits publish, and every Commit.
- Challenge. The adversary names two honest accounts and an Exit request (asset, amount, destination, options). The challenger draws and executes the Exit from .
- Admissibility. The challenger runs every subsequent query in both worlds, and , and answers it only if the leakage it produces is identical in both; otherwise the query is refused. may not be corrupted, and Receipts and Viewing-key disclosures of are not available.
- Output. The adversary outputs . Its advantage is .
Admissibility rules out the trivial wins: if could not afford the Exit, or a later Intent of would be funded in one world and not the other, the difference would appear in , and that is the leakage the statistical sections measure, not a break of the cryptography.
Theorem 8.9 (Unlinkability). Let the Coprocessor be realized by an enclave whose integrity and confidentiality hold except with advantage (Chapter 5), let the Intent encryption be IND-CCA2 with advantage , let the Ledger ciphertexts be IND-CPA with advantage under nonce discipline (Chapters 3 and 4), let Commits follow the rewrite discipline, and let the adversary hold fewer than Council shares. For any adversary making at most Intent and Exit requests and observing at most leaf ciphertexts,
Proof. We move from the real game with to a game whose view is a function of alone, then back to by the same steps in reverse. Each hop changes the adversary’s output distribution by at most the stated term.
Hybrid 0. The real game with .
Hybrid 1. Replace the Coprocessor by an ideal functionality that receives plaintext Intents and Exit requests over a private channel, computes Crossings and Exits by the specification of Chapter 7, and outputs only signed Residual orders, Exit transfers and Commits. The adversary’s view changes by at most , by the integrity and confidentiality of the enclave: the enclave’s outputs are the specified function of its inputs, and its memory and sealed keys are not observable.
Hybrid 2. Replace every Intent and Exit ciphertext from an honest account by an encryption of the all-zero message of the same padded length under , while the functionality still receives the true plaintexts. A distinguisher between consecutive sub-hybrids yields an IND-CCA2 adversary against the Intent encryption: the reduction answers decryption queries for adversarial ciphertexts through its decryption oracle, which is exactly what the adversary’s own Intents require, and embeds the challenge ciphertext at one position. A hybrid over positions costs .
Hybrid 3. Replace every honest account’s leaf ciphertext in every Commit by an encryption of zero under fresh randomness. Leaf keys are held inside the ideal functionality, so a distinguisher yields an IND-CPA adversary against the Ledger encryption; nonce discipline ensures each encryption uses a fresh nonce, the condition under which AES-256-GCM’s confidentiality bound applies. A hybrid over ciphertexts costs . The rewrite pattern is an element of under the rewrite discipline, and the leaves are now independent of balances.
Hybrid 4. Replace the adversary’s Council shares by uniformly random field elements. With fewer than shares of a Shamir sharing, the shares are uniformly distributed and independent of the secret (Chapter 6), so this change is perfect. The Council’s public outputs in the execution, which arise only in an Escape, are simulatable from and the decryption proofs of Chapter 6, whose zero-knowledge simulators are perfect or statistical; we absorb this in .
In Hybrid 4 every component of the view is either an element of , a ciphertext of a fixed message, a signature by the ideal functionality on a message determined by (Residual orders and Commit roots over zero-ciphertexts), or uniform randomness. The view is therefore a function of and independent randomness. By admissibility, is identical for and , so Hybrid 4 is identically distributed for both values of . Reversing Hybrids 3 through 0 with gives the factor 2 in (8.5).
Theorem 8.9 is the formal statement of what the earlier sections assumed: against , and , Privium leaks exactly , and every quantitative bound in this chapter is a bound on what says. Corruption of accounts in is already in the game, which is why the anonymity set of Definition 8.2 counts honest accounts only.
Corollary 8.10 (Unlinkability with countermeasures). Under the assumptions of Theorem 8.9, for a denominated, delayed Exit piece of denomination class , any adversary’s probability of identifying its source deposit is at most
and, for a Ring exit, at most the minimum of this quantity and the Ring’s own linking probability.
Proof. By Theorem 8.9 the adversary’s view is, up to the cryptographic terms, a function of . Within the piece’s amount identifies only its class (Theorem 8.4), and within the class Corollary 8.6 bounds timing linkage by ; Proposition 8.7 (a) shows the Residuals add no information distinguishing honest accounts with equal public records. The rewrite pattern helps only if the adversary follows the piece’s leaf from the batch that credited the deposit to the batch that debits the Exit, which by Proposition 8.7 (b) it does with probability at most ; a union bound adds that term. Lemma 8.8 gives the Ring statement.
Example
This is an example with illustrative inputs; none of its figures are measurements of Privium or of Solana.
Take one denomination class of USDC in which honest deposits arrive at per slot, and the recommended mean delay slots. Then , and (8.4) gives a timing adversary at most chance of naming the source deposit of a piece, or at least bits of average min-entropy; the rewrite term of (8.6) adds at most at . Doubling either the deposit rate or the mean delay adds one bit.
For contrast, suppose the same trader exits an exact, unique amount with no delay, one slot after depositing it. The amount alone singles out the deposit, so the posterior has min-entropy zero, and no Pool size helps. The same trader with denominations and the default delay receives (8.6), and routing the Exit through an anonymous Ring caps the link by the Ring’s own bound as well (Lemma 8.8). The difference between those two outcomes is a pair of defaults the trader does not have to set.
References
- A. Serjantov, G. Danezis, “Towards an Information Theoretic Metric for Anonymity”, Privacy Enhancing Technologies (PET), 2002. https://doi.org/10.1007/3-540-36467-6_4
- C. Díaz, S. Seys, J. Claessens, B. Preneel, “Towards Measuring Anonymity”, Privacy Enhancing Technologies (PET), 2002. https://doi.org/10.1007/3-540-36467-6_5
- G. Smith, “On the Foundations of Quantitative Information Flow”, FoSSaCS, 2009. https://doi.org/10.1007/978-3-642-00596-1_21
- G. Kappos, H. Yousaf, M. Maller, S. Meiklejohn, “An Empirical Analysis of Anonymity in Zcash”, USENIX Security Symposium, 2018. https://www.usenix.org/conference/usenixsecurity18/presentation/kappos
- Z. Wang, S. Chaliasos, K. Qin, L. Zhou, L. Gao, P. Berrang, B. Livshits, A. Gervais, “On How Zero-Knowledge Proof Blockchain Mixers Improve, and Worsen User Privacy”, ACM Web Conference (WWW), 2023. https://arxiv.org/abs/2201.09035
- S. Meiklejohn et al., “A Fistful of Bitcoins: Characterizing Payments Among Men with No Names”, ACM Internet Measurement Conference, 2013. https://doi.org/10.1145/2504730.2504747
- “Photon vs Axiom: Solana Memecoin Terminal Comparison (2026)”, MadeOnSol, 2026. https://madeonsol.com/blog/photon-vs-axiom-solana-trading-terminal
- J. D. C. Little, “A Proof for the Queuing Formula: L = λW”, Operations Research 9(3), 1961. https://doi.org/10.1287/opre.9.3.383
- “Solana Privacy Rings”, Helius, 2026. https://www.helius.dev/blog/solana-privacy-rings
- N. Lokhande et al., “Encifher: A Trusted-Execution Coprocessor for Confidential Computation on Solana”, IACR ePrint 2026/1504, July 2026. https://eprint.iacr.org/2026/1504