Fees
Every fee the protocol charges and everything it pays out. Most of what follows is decided and documented but not yet collected or paid, and each row says which it is — a fees page that read as if it were all live would be the most consequential kind of wrong.
Devnet only. Every fee is a governance parameter, never a constant.
What you pay
Three fees, and they do not fall on the same party. A buyer pays only on a completed trade and nothing to raise a dispute; a merchant carries the standing costs of advertising and being arbitrated.
Settlement fee
Charged today- Payer
- Buyer
- Amount
- 0.85% of the traded amount, in the stablecoin traded
Deducted from the stablecoin released to the buyer, so it is paid only when a trade actually completes. It splits 40/30/20/10 across the development, ecosystem, infrastructure and emergency-reserve treasuries. This is the one fee the protocol charges today, and it has been proven end to end on devnet.
Ad-listing fee
Specified, not yet active- Payer
- Merchant, from their liquidity vault
- Amount
- 1 OPEN (proposed)
Not charged yet. The field exists on-chain and is read by no instruction, so publishing an advertisement currently costs nothing. If you are planning merchant economics, treat this as a cost that is coming rather than one you are paying.
Arbitration deposit
Specified, not yet active- Payer
- Merchant, from their liquidity vault — whoever opened the dispute
- Amount
- 20 OPEN (proposed)
Forfeited to the arbitration pool only if the outcome goes against the merchant; otherwise it returns to their vault. The asymmetry is deliberate: a buyer is often a one-time participant, and making them fund a deposit to be heard would price the dispute mechanism out of reach of the party it exists to protect. Not charged yet — stored on-chain, read by no instruction.
What each role receives
Consumption and compensation are separate questions. A service can be free to consume and still be paid for by the protocol — that is exactly how oracle rates work.
Node operator
Specified, not yet active- Consumer pays
- —
- Provider receives
- A protocol reward proportional to stake × connectivity × availability
A node bridging to Solana counts 1.0 against 0.4 for one only gossiping, because it does strictly more work and the difference is externally observable rather than self-reported. The calculation exists and nodes publish the liveness observations it runs on, but nothing submits the result and the rewards vault is empty — so no node has been paid.
Arbitrator
Specified, not yet active- Consumer pays
- —
- Provider receives
- A share of the arbitration pool, pro-rata by revealed weight, for voting with consensus
Not built. Today voting costs transaction fees and returns nothing, while voting against consensus carries no penalty either — the incentive the commit-reveal design assumes is not yet in place.
Notification gateway
Specified, not yet active- Consumer pays
- Per delivery, by the participant who enabled notifications
- Provider receives
- That fee
Not metered. Nothing counts deliveries, so nothing can be charged or paid. The mechanism to receive it exists; the meter in front of it does not.
Oracle provider
Specified, not yet active- Consumer pays
- Nothing — reads are free
- Provider receives
- Paid by the protocol, scaled by currency coverage and uptime
Reads are free by decision, not by omission: a priced rate feed gets consulted less, which makes the median it contributes to thinner and easier to move. The provider is paid by the protocol instead, so the rate stays free at the point of use while its supply is still funded. The formula is proposed and not final, and nothing pays it yet.
Snapshot provider
Nothing, by decision- Consumer pays
- Nothing — downloads are free
- Provider receives
- Nothing
No revenue, and none planned. Serving a snapshot is a marginal cost on infrastructure a node operator already runs and is already compensated for. Anyone weighing a standalone snapshot service should read this as: there is nothing to earn here.
Risk intelligence provider
Specified, not yet active- Consumer pays
- Nothing directly
- Provider receives
- From the treasury: a 1,000 USDC per month base, plus an amount scaling with the number of wallets processed, all scaled by uptime
The only permissioned role: a provider must be approved by governance before operating. Every other role is permissionless because a bad actor's cost is bounded — a useless oracle is outvoted by the median, a dead gateway simply fails to deliver. A standing subscription drawn from the treasury has no such bound, so gating who may receive it is the condition that lets a paid slot exist at all. Pay scales with wallets processed rather than nodes served, because one flagged wallet read by a thousand nodes is a single piece of work — and a wallet only counts when it was screened against real protocol activity, never because a provider chose to publish a record naming it. Neither the payment nor the approval gate is built yet.
The one permissioned role
Risk intelligence is the only role that requires governance approval before operating. AllenHark is the default provider.
Default service key
ALLENLMtV1zEAHT3xpVryqcbdPCB8c9JhM1Jdbe5XHg5
Every fee is a parameter
No amount here is a constant. Each one is governance-updatable, because fees denominated in a token have to move as that token's price does. The figures shown are current defaults, and those marked as proposed have not been signed off.