Token & Fee Flow
Canonical specification of the MERA token, protocol execution fee schedule, and on-chain Jupiter buyback-and-burn flow.
This page is the single canonical specification for the MERA token and how protocol execution fees flow through the market.
MERA token parameters
| Parameter | Value |
|---|---|
| Name | Mera |
| Ticker | MERA |
| Total supply | 1,000,000,000 (fixed) |
| Launch model | Fair launch with developer allocation |
| Developer allocation | Developer's first buy at launch on the same terms as every buyer (allocation share set at launch) |
| Fee allocation | 100% of protocol execution fees buy MERA on the market via Jupiter and burn it |
| Mint address | Configured at mainnet launch |
| Launch venue | Configured at mainnet launch |
The full 1,000,000,000 supply enters the public launch directly. The developer allocation is the developer's own first buy in that launch on the same terms as every buyer, with its share set as a launch configuration point.
Protocol execution fee schedule
Mera charges a protocol execution fee in the settlement asset on every cleared trade. Non-execution actions carry zero protocol fee.
| Action | Program instruction | Fee rate | Settlement asset debited |
|---|---|---|---|
| Instant confidential swap | settle_confidential_swap | FEE_BPS (10 bps / 0.10% default) | Output mint (output_vault) |
| Hidden-size limit order fill | fill_hidden_order | FEE_BPS (10 bps / 0.10% default) | Taker payment mint (taker_vault) |
| Sealed RFQ block trade | settle_sealed_rfq | FEE_BPS (10 bps / 0.10% default) | Output mint (output_vault) |
| Shield deposit | deposit_shielded | 0 bps | None |
| Unshield withdrawal | withdraw_shielded | 0 bps | None |
| Hidden-size order cancel or expiry | cancel_hidden_order | 0 bps | None |
FEE_BPS is stored on chain in ProtocolConfig.fee_bps and capped in mera_core at MAX_FEE_BPS = 500 (5.00%). The localnet development default is 10 bps (0.10%); the mainnet rate is a launch configuration point set via init_protocol and adjustable by ProtocolConfig.admin through update_protocol_fee.
Exact on-chain fee math
In mera_core, protocol fees are computed with integer floor division in u128 so the rounding stays with the user:
fee_paid = floor(gross_settlement_amount * fee_bps / 10_000)
net_received = gross_settlement_amount - fee_paidWhen fee_paid > 0, the settlement instruction transfers fee_paid directly from the Ring's ShieldedVault token account to fee_recipient_token_account (the associated token account of ProtocolConfig.fee_recipient) in the same atomic transaction, decrements ShieldedVault.total_shielded, and increments ShieldedVault.total_fees_collected.
Buyback and burn flow
- Every settled swap, hidden-order fill, and sealed RFQ transfers its protocol fee on chain directly to
ProtocolConfig.fee_recipient(Mera's launch wallet). mera_corecontains no on-chain buyback instruction, keeping settlement transactions fast and independent of external DEX accounts.- Mera's off-chain keeper runs a scheduled buyback-and-burn crank (
mera-buyback-burn) every 60 seconds onceMERA_MINTis configured at launch. UntilMERA_MINTis set, the crank stays dormant (buybackStatus: "dormant"onGET /v1/stats). - When spendable balance above the
0.05 SOL(50,000,000lamports) rent and transaction fee reserve meets the minimum buyback threshold, the crank requests an exact-in swap quote fromJupiter(slippageBps: 100,maxAccounts: 40), executes the swap, and appendscreateBurnCheckedInstructionin the same transaction to burn the exactquote.minimumOutdelivered by the swap. - Burning only
quote.minimumOutper crank run guarantees that any separate token balance held by the wallet is untouched while100%of boughtMERAis permanently removed from supply.
Verifying fee flow on chain
- Read
GET /v1/statsorGET /healthto inspect the activefeeBps,feeRecipient,buybackStatus, andmeraMint. - Verify any individual trade's exact
feeAmount,feeBps, andfeeRecipientby decrypting its Transaction Viewing Key in Receipts or callingPOST /v1/receipts/verify. - Inspect
ShieldedVault.total_fees_collectedon any Ring vault PDA (["vault", ring_pubkey, mint_pubkey]) to reconcile cumulative fees collected per Ring and mint.