Mera
ExecutionInstant confidential swapsClear from encrypted balances in one 150ms slot.Hidden-size limit ordersLock encrypted size in a private escrow PDA.Sealed RFQ block tradesRequest signed quotes without leaking size.
Vault & AuditShielded vault & keysDeposit SOL, SPL, or Token-2022 into a Ring.Viewing key verifierDecrypt and prove a single settled fill.
Docs/Protocol & Reference
3 min read

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

ParameterValue
NameMera
TickerMERA
Total supply1,000,000,000 (fixed)
Launch modelFair launch with developer allocation
Developer allocationDeveloper's first buy at launch on the same terms as every buyer (allocation share set at launch)
Fee allocation100% of protocol execution fees buy MERA on the market via Jupiter and burn it
Mint addressConfigured at mainnet launch
Launch venueConfigured 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.

ActionProgram instructionFee rateSettlement asset debited
Instant confidential swapsettle_confidential_swapFEE_BPS (10 bps / 0.10% default)Output mint (output_vault)
Hidden-size limit order fillfill_hidden_orderFEE_BPS (10 bps / 0.10% default)Taker payment mint (taker_vault)
Sealed RFQ block tradesettle_sealed_rfqFEE_BPS (10 bps / 0.10% default)Output mint (output_vault)
Shield depositdeposit_shielded0 bpsNone
Unshield withdrawalwithdraw_shielded0 bpsNone
Hidden-size order cancel or expirycancel_hidden_order0 bpsNone

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:

text
fee_paid = floor(gross_settlement_amount * fee_bps / 10_000)
net_received = gross_settlement_amount - fee_paid

When 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

  1. Every settled swap, hidden-order fill, and sealed RFQ transfers its protocol fee on chain directly to ProtocolConfig.fee_recipient (Mera's launch wallet).
  2. mera_core contains no on-chain buyback instruction, keeping settlement transactions fast and independent of external DEX accounts.
  3. Mera's off-chain keeper runs a scheduled buyback-and-burn crank (mera-buyback-burn) every 60 seconds once MERA_MINT is configured at launch. Until MERA_MINT is set, the crank stays dormant (buybackStatus: "dormant" on GET /v1/stats).
  4. When spendable balance above the 0.05 SOL (50,000,000 lamports) rent and transaction fee reserve meets the minimum buyback threshold, the crank requests an exact-in swap quote from Jupiter (slippageBps: 100, maxAccounts: 40), executes the swap, and appends createBurnCheckedInstruction in the same transaction to burn the exact quote.minimumOut delivered by the swap.
  5. Burning only quote.minimumOut per crank run guarantees that any separate token balance held by the wallet is untouched while 100% of bought MERA is permanently removed from supply.

Verifying fee flow on chain

  • Read GET /v1/stats or GET /health to inspect the active feeBps, feeRecipient, buybackStatus, and meraMint.
  • Verify any individual trade's exact feeAmount, feeBps, and feeRecipient by decrypting its Transaction Viewing Key in Receipts or calling POST /v1/receipts/verify.
  • Inspect ShieldedVault.total_fees_collected on any Ring vault PDA (["vault", ring_pubkey, mint_pubkey]) to reconcile cumulative fees collected per Ring and mint.