KALO Token & Fee Burn
KALO fixed supply, fair launch model, protocol fee routing on settled SealedEscrow payouts, and Jupiter buyback-and-burn.
Token parameters
| Parameter | Value |
|---|---|
| Name | Kalo |
| Ticker | KALO |
| Chain | Solana |
| Supply | 1,000,000,000 (fixed) |
| Launch model | Fair launch with a developer allocation bought on equal terms in the launch |
| Developer allocation share | Launch 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:
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:
ring_vaulttransfersprovider_payouttoprovider_token_account.ring_vaulttransfersfee_amountdirectly tolaunch_wallet_token_account(verified on-chain againstprotocol_config.launch_wallet).protocol_config.total_fees_collectedincrements byfee_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.
kalo_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:
- Requests an exact-in quote from Jupiter (
quoteExactIn) swapping collected settlement fees (inputMint->KALO_MINT, defaultslippageBps: 100,maxAccounts: 40). - Fetches the swap transaction instructions (
setup,swap,cleanup, and address lookup tables) withtaker = launch_wallet. - Appends an SPL Token
createBurnInstructiontargeting the launch wallet'sKALOassociated token account forquote.minimumOut. - Submits the combined transaction so the
KALOdelivered by the market swap is burned immediately, without ever touching any pre-existingKALObalance held in the launch wallet.
Verifying fee flows
Anyone can audit protocol fee flows on Solana:
- Read
ProtocolConfig(["protocol_config"]under7gvg3hFxPbtSkxjCoPHEXMPSen7X9H21y96JPVBbf47S) forfee_bps,launch_wallet,total_escrows_settled, andtotal_fees_collected. - Inspect
GET /v1/protocol/statsfor liveprogramId,launchWallet,kaloMint,feeBps, andsettledEscrows. - Inspect
HyCMuwjbYvFWkJvw4MQY2EEJo8ZHseSBoqLoWdphGYUwon Solana Explorer for incoming fee transfers and outgoing Jupiter swap-and-burn transactions onceKALO_MINTis live.