Every Commit pays the Crossing’s fees to the token’s launch wallet, and a crank signing as that wallet buys $PRV through Jupiter with them and burns exactly what each buy delivered. This page holds the builder’s facts: where the fee is charged, who receives it, how the crank runs, and how to reconcile each step on chain. What a trader pays is in Fees; Pool shows the flow live.
The token#
| Name and ticker | Privium, PRV |
| Mint | 9FSjffoh8Yk8jdpr9EEEuxTD6mphYayfboxZMKWVPRV |
| Supply | 1,000,000,000 PRV at 6 decimals, 10^15 base units |
| Authorities | Mint and freeze authority revoked; metadata immutable |
| Market | Raydium CPMM pool against ZEC, 7PscVHXMuzSDK1Abz2rP3BrunEjNYdJtc5aNxS1htnDQ |
| Launch | Fair launch with a developer allocation: the developer’s own first buy at launch, on the same terms as every buyer |
With the mint authority revoked no instruction can add to the supply, so it only falls, by each burn.
Where the fee is charged#
The fee rate is fee_rate_bps in the Pool’s PoolConfig, in basis points, at most 10,000. Privium’s is 10 bps, 0.10%. The API serves it as feeBps in GET /v1/config and on each market panel, and the order ticket shows the fee it implies before every order.
The Coprocessor charges it inside the Crossing, on every fill: times the filled size times the fill price, in the pair’s quote asset (SOL or USDC). Both sides of a crossed fill pay it, and a routed fill pays the same rate. Each trader’s fee is rounded down to whole base units of the quote asset, and the Crossing’s fee in each asset, , is the exact sum of those fees. It leaves the trader’s encrypted balance in the Crossing’s state transition and enters the signed Commit message as each asset’s fees field (Commit).
The fee recipient#
PoolConfig.fee_recipient is the token’s launch wallet. It is set by initialize, and only the admin key PoolConfig names changes it, with set_fee_recipient; the admin sets the rate with set_fee_rate (Instructions).
commit pays each asset’s fees from that asset’s vault shard 0 to the fee recipient’s associated token account, which the program derives from the fee recipient, the mint’s token program and the mint, and requires in the asset’s account group. The Pool authority signs the transfer, and it runs before the Commit’s conservation check, so at every committed root the vaults hold trader balances, committed Exits and uncredited deposits only. The program has no fee vault, no fee accrual and no instruction that sweeps fees or buys the token.
Buyback and burn#
A crank on Privium’s keeper signs as the launch wallet, the key PoolConfig names as fee_recipient. It works in fixed intervals of slots, spends at most a set cap per swap, and quotes every swap with a slippage bound.
In each interval the crank takes wrapped SOL, then USDC, and for each:
Size the swap#
The amount is the least of three: the launch wallet’s balance in that asset, the fees the verified Commits paid it in that asset less what earlier buybacks spent, and the cap. The crank spends fees only, never another balance the wallet holds.
Swap through Jupiter#
It quotes the amount in for $PRV out with the slippage bound and sends the swap, signed by the launch wallet, with the memo
privium:buyback. Jupiter routes it from SOL or USDC through ZEC into the PRV/ZEC pool, where $PRV trades.Measure the delivery#
From the confirmed swap transaction’s own token balances, it records the $PRV the wallet gained and the input it spent.
Burn exactly that#
It burns the measured amount with the SPL Token
Burninstruction in a second transaction signed by the launch wallet, with the memoprivium:burn:<swap signature>, and confirms that the burn’s balance change equals it. No new swap starts while a bought amount waits to be burned.
The burn is the measured delivery of its own swap, never a balance the wallet held before, so the developer’s first buy, held in the same wallet, is never part of it.
Reconciling it on chain#
Fees per Commit#
Each Commit transaction carries, per asset, a token transfer of that asset’s
feesfrom vault shard 0 to the recipient’s token account; the same amount is in the signed Commit message the Ed25519 instruction before it verifies. The API lists them per Crossing asfees, each with mint, amount, recipient and transaction (Crossing).The recipient’s balance#
The recipient’s wrapped SOL and USDC token accounts receive exactly the Commits’ fee transfers, and spend only into the crank’s swaps.
Each buyback#
Each swap spends at most the cap, and its burn destroys exactly the $PRV the swap delivered. The API lists each pair as a
Buyback: input mint and amount, bought and burned amounts, and both transactions.Supply#
The supply of mint
9FSjffoh8Yk8jdpr9EEEuxTD6mphYayfboxZMKWVPRVis 1,000,000,000 PRV, 10^15 base units at 6 decimals, less every burn. The mint account’ssupplyfield shows the current figure; the API reports the total burned assupplyBurnedin the token panel, in base units, and the two always add up to 10^15.
Summed over a period, the burns equal the period’s fees divided by the average price the buys paid, as the whitepaper’s Equation (12.20) states.