Protocol

KALO Token & Fee Burn

KALO fixed supply, fair launch model, protocol fee routing on settled SealedEscrow payouts, and Jupiter buyback-and-burn.

Token parameters

ParameterValue
NameKalo
TickerKALO
ChainSolana
Supply1,000,000,000 (fixed)
Launch modelFair launch with a developer allocation bought on equal terms in the launch
Developer allocation shareLaunch configuration point (set at token launch)
Protocol fee rate (ProtocolConfig.fee_bps)Launch configuration point (hard ceiling MAX_FEE_BPS = 1000 / 10%)
Token mint (KALO_MINT)Set at token launch
Fee recipient (ProtocolConfig.launch_wallet)HyCMuwjbYvFWkJvw4MQY2EEJo8ZHseSBoqLoWdphGYUw

How KALO launches

The entire 1,000,000,000 fixed supply of KALO enters the public fair launch. The developer allocation is the developer's own first buy in that launch, made from the launch wallet on the same terms as every other participant. The exact developer allocation share and token mint address are configured at launch and published in site/src/lib/facts.ts once live.

Protocol fee routing on-chain

Every settled HTTP 402 call (settle_with_receipt) calculates the protocol fee from ProtocolConfig.fee_bps:

rust
let fee_amount = ((amount as u128) * (protocol_config.fee_bps as u128) / 10_000u128) as u64;
let provider_payout = amount - fee_amount;

Fee rounding always favors the service provider (integer floor on fee_amount). In the same settle_with_receipt transaction:

  1. ring_vault transfers provider_payout to provider_token_account.
  2. ring_vault transfers fee_amount directly to launch_wallet_token_account (verified on-chain against protocol_config.launch_wallet).
  3. protocol_config.total_fees_collected increments by fee_amount.

Any SOL fees accrued directly in ProtocolConfig above rent-exempt minimum can be swept to launch_wallet by the admin via claim_protocol_fees.

NOTEkalo_protocol itself contains no swap or buyback instruction. All on-chain settlement instructions keep compute usage low and route fees cleanly to launch_wallet.

Off-chain Jupiter buyback-and-burn

Kalo's keeper worker (backend/src/keeper/buyback.ts) holds the launch_wallet signer and runs the buyback-and-burn cycle once KALO_MINT is configured:

  1. Requests an exact-in quote from Jupiter (quoteExactIn) swapping collected settlement fees (inputMint -> KALO_MINT, default slippageBps: 100, maxAccounts: 40).
  2. Fetches the swap transaction instructions (setup, swap, cleanup, and address lookup tables) with taker = launch_wallet.
  3. Appends an SPL Token createBurnInstruction targeting the launch wallet's KALO associated token account for quote.minimumOut.
  4. Submits the combined transaction so the KALO delivered by the market swap is burned immediately, without ever touching any pre-existing KALO balance held in the launch wallet.

Verifying fee flows

Anyone can audit protocol fee flows on Solana:

  • Read ProtocolConfig (["protocol_config"] under 7gvg3hFxPbtSkxjCoPHEXMPSen7X9H21y96JPVBbf47S) for fee_bps, launch_wallet, total_escrows_settled, and total_fees_collected.
  • Inspect GET /v1/protocol/stats for live programId, launchWallet, kaloMint, feeBps, and settledEscrows.
  • Inspect HyCMuwjbYvFWkJvw4MQY2EEJo8ZHseSBoqLoWdphGYUw on Solana Explorer for incoming fee transfers and outgoing Jupiter swap-and-burn transactions once KALO_MINT is live.

Confidential commerce infrastructure for autonomous software.

Shielded treasuries, scoped mandates, and receipt-bound HTTP 402 settlement on Solana L1.

Open consoleRead the docs