Fees and the treasury
Where trading fees go, what each vault does, and how collection reaches the protocol.
On this page
Protocol receipts versus total trading costEvery received fee has a destinationSeparate budgets, separate responsibilitiesHow fees are collected01Protocol receipts versus total trading cost
The ordinary design allocates 5% of eligible trading volume to ComputeWorks receipts: a 4.30% creator tax plus a 0.70% creator share of the venue's base fee. The venue retains a separate 0.30% under that schedule. These amounts should not be confused with the percentages used to split the protocol's receipts.
Opening purchases can have additional taxes, and swaps can incur network fees, price impact, or other execution costs. The actual transaction quote is the reference for the cost of a trade. The receipt-split example below is not a swap quote.
02Every received fee has a destination
For an illustrative 1,000 USDG received by the protocol:
| Destination | Share | Example |
|---|---|---|
| Acquisition vault | 80% | 800 USDG |
| Team vault | 10% | 100 USDG |
| Reserve vault | 10% | 100 USDG |
03Separate budgets, separate responsibilities
The Acquisition vault holds funds for approved hardware purchases and procurement costs. The Team vault supports operations and receives eligible inference-cost reimbursements through the settlement process. The Reserve vault backs approved support commitments and working capital.
The Holder Payout vault separately holds the funds backing credit allocations and settlements. An unallocated treasury balance is not automatically a holder entitlement. Reserved hardware funds and funded holder obligations cannot be treated as the same spending budget.
04How fees are collected
An online keeper submits transactions to collect supported fee receipts and move them through the protocol's accounting and vault split. The ordinary collection path can sweep, claim, and flush receipts atomically, so the supported steps either complete together or revert.
Some external, opening, or graduation receipts require authenticated evidence, publication, and a review delay before collection. They retain their own accounting category; an unexplained balance is not automatically labeled ordinary trading revenue.
Smart contracts do not wake themselves up. Collection depends on a running, funded keeper, functioning RPC access, valid source evidence, and unpaused contracts. A polling interval is not a guarantee that every balance will arrive in the treasury immediately.