Comisiones

• Settlement fee

  Cobrada hoy

  Pagador

  Buyer

  Cantidad

  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

  Especificada, aún no activa

  Pagador

  Merchant, from their liquidity vault

  Cantidad

  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

  Especificada, aún no activa

  Pagador

  Merchant, from their liquidity vault — whoever opened the dispute

  Cantidad

  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.

• Node operator

  Especificada, aún no activa

  Paga el consumidor

  —

  Recibe el proveedor

  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

  Especificada, aún no activa

  Paga el consumidor

  —

  Recibe el proveedor

  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

  Especificada, aún no activa

  Paga el consumidor

  Per delivery, by the participant who enabled notifications

  Recibe el proveedor

  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

  Especificada, aún no activa

  Paga el consumidor

  Nothing — reads are free

  Recibe el proveedor

  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

  Nada, por decisión

  Paga el consumidor

  Nothing — downloads are free

  Recibe el proveedor

  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

  Especificada, aún no activa

  Paga el consumidor

  Nothing directly

  Recibe el proveedor

  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.

Ninguna cantidad aquí es una constante. Cada una es actualizable por gobernanza, porque las comisiones denominadas en un token tienen que moverse como se mueve el precio de ese token. Las cifras mostradas son valores predeterminados actuales, y las marcadas como propuestas no se han aprobado.