Kaia’s token economy is a perpetual treasury machine

Kaia’s design decision is blunt: it diverts a large, ongoing share of block rewards into protocol-controlled funds. With every new block, newly issued KAIA plus transaction fees used in the block are aggregated and distributed, with 25% to the Kaia Ecosystem Fund (KEF) and 25% to the Kaia Infrastructure Fund (KIF). That is a structural commitment to “always-on” ecosystem and foundation financing, not a one-time war chest.

KAIA itself is the chain’s native asset for paying transaction fees and for staking to secure the network. The whitepaper also frames KAIA’s utility and value support as a function of usage and burning, with an explicit “3-Layer Burn Model” concept that includes protocol burns plus ecosystem and business-linked burns.

From a treasury risk manager’s lens, the key question is not whether Kaia can fund growth. It can, by construction. The harder question is whether the system can credibly bound dilution and discretionary spend over multi-year horizons, while keeping governance incentives aligned with long-term holders.

If you want a simple framework for evaluating these flows, start with the token economy components that show up in most credible designs.

Supply, issuance, and genesis distribution

Kaia mainnet mainnet launched on August 29, 2024. KAIA was created through the integration of Klaytn’s KLAY and Finschia’s FNSA at the time of integration, using an exchange rate of 1 KLAY : 1 KAIA and 148.079656 FNSA : 1 KAIA (equivalently, FNSA:KAIA = 148.079656:1).

Issuance is inflationary. Kaia’s per-block issuance is 9.6 KAIA minted per block, implying roughly ~300,000,000 KAIA per year, described as 5.2% annual inflation against the “total KAIA tokens in the market,” and explicitly noted as governance-changeable. The same source reiterates that the per-block issuance is not permanently set and can be changed via governance voting.

Market trackers reflect this open-ended supply posture. CoinGecko lists KAIA’s Max Supply as ∞ and reports Total Supply 5,856,641,936 and Circulating Supply 5,856,641,747 (as shown on its KAIA page).

Initial distribution at integration (from the Kaia whitepaper’s estimated integration figures):

The integration estimates also state that, at conversion, because the uncirculated amount is burned, “the total supply and the circulating supply match,” with an estimated circulating supply at integration of about 5,768M KAIA. That figure is a starting point. Inflation and burn policy then drive divergence over time.

Where fees go: burn, reward pool, and fund flows

Kaia’s core cashflow loop is straightforward. Each block produces a “block reward” that includes (1) minted KAIA and (2) transaction fees used in that block. That combined reward is distributed 50% to Validators and Community, 25% to KEF, and 25% to KIF. Within the 50% bucket, the docs break down 10% of total to block proposer rewards and 40% of total to staking rewards.

This is the part many models miss: Kaia does not treat “ecosystem funding” as an optional treasury drawdown. It is a first-class recipient of block rewards. That means ecosystem funding scales with chain activity and time, whether the ecosystem is in boom mode or not.

On the burn side, Kaia has two overlapping descriptions that matter for supply outcomes. First, the whitepaper describes “Transaction-Based Burning” as a default where “a portion of the transaction fee is automatically burned,” and it explicitly states the burn extent is adjusted through on-chain governance consensus. Second, the Transaction Fees docs specify protocol-level gas fee burning behavior by hardfork: since Magma hardfork, half of the block gas fee is burnt, and since Kore hardfork, most of the block gas fee is burnt.

Kaia’s newer fee UX also shapes fiscal flows. A Kaia docs cookbook explains that after the Kaia hard fork, gasPrice is “base fee + priority fee,” that the base fee is burned, and that the priority fee contributes to the network’s reward pool which is later distributed to validators and ecosystem funds. This is treasury-relevant: in high activity periods, fees can become an additional funding stream for KEF and KIF on top of inflation.

Finally, the whitepaper’s validator reward mechanism includes explicit fee burn conditions at the block level: if total transaction fees in a block are less than the block reward, the fees are burned, and if transaction fees exceed the block reward, half of the exceeded amount is burned and half goes to the block proposer. In practice, your net inflation depends on both issuance and the realized burn regime, which can shift via governance and via network usage.

Treasury design: KEF vs KIF and budget controls

Kaia’s treasury is not one bucket. It is two, and they are governed differently.

KEF (Kaia Ecosystem Fund) is defined in the whitepaper as a sustainability resource for infrastructure, developer support, and indirect investment, and it receives 25% of KAIA issued when creating a block. The same section states KEF “can only execute funds for agreed purposes with prior approval from the governance,” with execution details transparently disclosed. The execution method is process-heavy: quarterly budgets by category require GC approval, and even within approved budgets, specific expenditures are individually GC-approved, then disclosed after use. This is closer to a controlled grants program than a discretionary foundation wallet.

KIF (Kaia Infrastructure Fund) is defined as a resource for R&D, ecosystem acceleration, and foundation operation, also receiving 25% of KAIA issued when creating a block. Its control model is looser: KIF is executed by the foundation “through an internal control system” after prior announcement of the budget plan by category, with details disclosed. This is normal in foundations, but it is a governance trade-off. Less friction can mean faster execution. It can also mean a wider gap between tokenholder expectations and operating reality.

What does this look like in practice? The governance forum shows KEF being used via discrete budget proposals. For example, governance proposal GP-10 (“Stablecoin Summer”) proposes allocating 60,000,000 KAIA for the initiative, with an explicit “as-needed” commitment and intent to return unused funds to the treasury. The forum also shows operational treasury movements. A KIF notice states a transfer of 22,268,129 KAIA from a KIF minting wallet to a KIF executor wallet, and explicitly notes that circulating supply remains unchanged because both wallets are included in circulating supply.

As a reserve manager, I treat those disclosures as positive signals. They indicate the team understands optics and auditability. The bigger issue is magnitude. With 50% of block rewards flowing to KEF and KIF combined, these funds are not “side programs.” They are the core fiscal engine.

Governance and parameter control

Kaia’s governance model is stake-weighted and designed around a Governance Council (GC) that also operates core infrastructure. The token economy docs state that to become a council member, a candidate must undergo qualification review and must stake at least 5,000,000 KAIA.

The Kaia governance docs specify voting power as 1 vote per 5M KAIA staked, allow public delegation from non-GC holders to GC members, and apply a cap so that maximum votes are “total valid GC members - 1” (example given: 40 members implies cap of 39 votes). This cap helps avoid pure plutocracy at the extreme, but it does not remove concentration risk. It mainly changes the shape of it.

Process matters as much as the math. Kaia’s governance process outlines a three-step flow: discussion in the governance forum, then on-chain registration and voting once there is at least one positive feedback from a GC member, then execution of approved proposals. The whitepaper and token economy docs also emphasize that key parameters like annual inflation and per-block issuance can be changed through governance voting.

For tokenholders, that means “tokenomics” is not a static PDF artifact. It is a governed policy surface. Treasury risk lives in those knobs.

Risk register: dilution, governance capture, and fiscal opacity

Dominant risk: persistent dilution pressure driven by treasury-directed emissions, with governance-controlled constraints that are real but not fully deterministic.

Kaia mints 9.6 KAIA per block and frames that as ~300M per year and 5.2% annual inflation, changeable via governance. By itself, that is not unusual for a PoS L1. The structurally unusual piece is the split: 50% of block rewards go to KEF and KIF combined, every block, continuously. If you are underwriting KAIA as an asset, you are underwriting the foundation’s and GC’s ability to convert that steady inflow into either (1) sustained network usage that increases fee burn and fee-derived demand, or (2) capital formation that compounds back into the ecosystem without becoming chronic sell pressure.

Kaia explicitly wants burn as a counterweight. The fee model burns the base fee, and Transaction Fees docs describe significant gas fee burning post-hardforks, including that “most of the block gas fee is burnt” since Kore. The whitepaper also frames transaction-based burning as governance-adjustable and extends burn concepts into MEV and business-based layers. That creates a moving target for “net inflation,” and it makes price and supply stability partly dependent on governance discipline during growth campaigns.

KEF has meaningful procedural controls, including quarterly category budgeting and GC approval of individual expenditures. That reduces pure discretion risk. KIF is foundation-executed with disclosure and internal controls, which is faster but puts more weight on institutional credibility and reporting quality. In a bear market, when organic demand is thin and “ecosystem acceleration” still wants to spend, the gap between emitted tokens and absorbable demand tends to widen. That is when treasury policies become survival policies.

My bottom line on the dominant risk is simple. Kaia’s treasury architecture is powerful, but it is also a permanent dilution conveyor belt unless burns and productive capital deployment keep pace. If governance ever decides to “solve” growth by raising issuance, or if fund spending becomes the primary driver of activity, you can get reflexive sell pressure that no amount of branding fixes. The model works best when treasury spending is counter-cyclical, tightly budgeted, and relentlessly measured against on-chain adoption outcomes. The docs support that intent. The chain’s long-run asset outcome depends on execution.

  1. Run-rate ecosystem spend overwhelms organic demand. Trigger: sustained KEF/KIF disbursements at a pace that exceeds organic fee demand and burn. Mechanism: half of block rewards accrue to KEF/KIF and become liquid supply when sold or distributed, increasing circulating supply faster than the market can absorb. Who bears it: spot holders and stakers (real yield gets diluted by price impact). Measurable indicators: net outflows from KEF/KIF operational wallets disclosed via Square and forum notices, size and frequency of large KEF budgets (example: 60,000,000 KAIA in GP-10), and rising exchange deposits from known treasury-linked addresses.
  2. Governance concentration shifts parameters against passive holders. Trigger: delegation and stake concentration leads to a small subset of GC members reliably controlling outcomes. Mechanism: stake-weighted governance (1 vote per 5M KAIA, capped) can still coordinate changes to inflation, fee parameters, and fund policies, reshaping net issuance and treasury flows. Who bears it: non-delegating holders and minority governance blocs. Measurable indicators: vote concentration near the cap, delegation concentration, and recurring parameter-change agendas affecting inflation or fee mechanics.
  3. Burn effectiveness is governance-variable and cycle-dependent. Trigger: low-usage periods (lower fee burn) or governance decisions that reduce burn intensity to increase validator revenue. Mechanism: net inflation rises if issuance stays constant while burned fees fall, or if burn parameters are adjusted. Who bears it: long-duration holders who rely on burn to offset issuance. Measurable indicators: on-chain burn as a percent of issuance, changes to fee policy and related KIPs, and divergence between “minted per block” and burned amounts over rolling 30 to 90 day windows.

If you want a quick cross-check against a very different design, use an emission model comparison as a sanity test for your dilution assumptions.

If you are advising teams building on Kaia, the practical playbook is to treat KEF and KIF like institutional budgets, not “community funds.” Model them like ongoing fiscal policy. Set explicit sell-pressure assumptions and stress-test them against low-activity regimes. This is where tokenomics design work looks like treasury planning, not vibes.

We also track these patterns and measurement approaches in our research reports, especially where net issuance depends on both governance and usage.

If you need targeted tokenomics consulting or a second set of eyes as a tokenomics advisor on treasury policy (spend controls, reporting cadence, and dilution guardrails), focus the scope on what governance can actually change and on what the funds are structurally entitled to receive per block.



This article is part of our Tokenomics Deep Dive series.