Status. Everything on this page is a proposal for registration under El Salvador's digital-asset framework and may change in that process. It is not an offer to sell any instrument, nor investment, legal or tax advice. Parameters carry the date they were set.
1. Overview
Data sharing between institutions needs infrastructure that none of them controls alone: where a permission is recorded once, enforced everywhere, and cannot be rewritten by the party that benefits. Kovo is that infrastructure for banks, fintechs and public institutions in Latin America. The KOVO asset is what ties the use of that infrastructure to its security and growth.
Two sides of the market
Institutions make their data ready once, keep it in their own Vault, and let it be used only under grants they issue, alone or as members of a Collective. Buyers and partners, including other institutions, regulators and model builders, receive results and scoped products under those grants, with lineage they can audit. Each institution that joins widens what buyers can reach; each buyer gives institutions one more reason to make data ready. Reach grows with the product of the two populations, not their sum.
What the protocol charges for
Grants are free. Fees are charged on what repeats: a result released from a Room, a workload run, a sale settled in the Market, a Forward originated. Each transaction type has its own rate, set as a parameter rather than a redeployment, so the fee base grows with use and with new transaction types, not with the number of users.
Where the fees go
Fees are paid in USD stablecoin. The largest share goes to the operators who validate the Ledger and run key and release services, pro rata to stake. A share buys KOVO on the market and burns it. The rest funds an ecosystem treasury for Collective formation, Bench capacity and audits.
2. Fees and where they go
2.1 Transaction types and rates
| Transaction | When | Proposed rate |
| Grant issuance | Per grant | Free |
| Result release | Per release from a Room under a grant | USD 0.05 per scope released |
| Room run | Per workload | 5% of the compute line |
| Market settlement | Per sale | 2% of the sale |
| Forward origination | Per instrument | 1% of the amount financed |
| Vault registration, data write | Once, as data is added | Unset (reserved) |
2.2 The unit
One use case in production releases results on a schedule. A daily scored release of one scope is 365 priced releases a year from a single preparation. At USD 0.05 each, that is USD 18.25 a year for one scope of one use case at one institution; a Collective running a fraud model across five members and releasing to each is five scopes. The fee base is small per release and grows with every use case that goes live and stays live.
2.3 How a fee splits
| Share | Goes to | Why |
| 60% | Operator pools, pro rata to stake | Validating the Ledger, running key and release services |
| 20% | Buyback and burn of KOVO | External income becomes demand for the asset; supply contracts with use |
| 20% | Ecosystem treasury | Collective formation grants, Bench training, audits |
2.4 How the parts feed each other
Usage to securityMore releases and sales, more fee income, more reason to stake, more operators.
Fees to scarcityFee income buys and burns KOVO; issuance is flat; beyond a level of use, net supply contracts.
Treasury to usageTreasury funds Collective formation and Bench capacity, which produce more prepared data and more releases.
Operators to reachOperator income attracts institutions and custodians to run validators, widening the trusted set.
3. Staking
Staking means delegating KOVO to a named operator. Operators are the validators of the Ledger and the parties who run key and release services: C² Labs, participating institutions, and audited custodians. Fee income is allocated across operator pools pro rata to stake, operators set a commission (default 10%) and pass on the rest. Running key and release services is paid separately as a service fee from platform revenue, so the commission does not have to cover real operating costs. A 7-day bonding period applies and rewards compound through automatic restaking. Slashing of delegated stake for operator misbehaviour is a target state, not a launch feature.
A delegator's yield therefore depends on five things: fee income, the 60% operator share, the delegator's share of total stake, the operator's commission, and the market value of staked KOVO. Doubling fee income doubles yield; doubling total stake or price halves it. Kovo will publish fee income monthly so that the first term is never a guess.
4. Buyback
A defined share of fee income, 20% at the proposed parameters, buys KOVO on the market and the purchased tokens are burned. The share is a parameter and scales only with fee income; every burn is published with its Ledger transaction.
4b. A dollar waterfall
USD 100,000 of Room compute billed to a customer at about 1.7× cost leaves Kovo a USD 41,176 margin. The 5% protocol fee, USD 5,000, comes out of that margin; the customer pays nothing extra. It splits USD 3,000 to operator pools (at 10% commission, USD 300 to operators and USD 2,700 to delegators), USD 1,000 to buyback and burn, and USD 1,000 to the treasury.
| Customer-funded protocol income per year | Amount | Basis |
| One deployment, no Market | ≈ USD 5,200 | USD 100k compute + 10 scopes released daily |
| 100 deployments | ≈ USD 518,000 | Same profile |
| Market sales of USD 10M | USD 200,000 | 2% settlement |
What that means. Protocol income is small while Kovo is a set of single-institution deployments, so operators are paid for running services through a separate service fee, and the asset only matters once Collectives and the Market carry volume. That is why KOVO launches at Stage 4 of the roadmap, gated on the fee base. Issuance (1.5M KOVO a year) is always reported on its own line, never as income.
5. Supply
| Allocation | Share | Terms |
| Ecosystem and Collectives | 35% | Released against Ledger-recorded contribution over ten years: formation grants, contribution incentives, Bench |
| Operator rewards | 15% | Flat annual issuance over ten years, independent of fees |
| C² Labs and team | 20% | Four-year vest, one-year cliff |
| Investors | 15% | Vesting under their agreements |
| Treasury reserve | 10% | Governance-controlled |
| Public distribution | 5% | Under the digital-asset framework, if and when registered |
Policy cap: 100,000,000 KOVO. Issuance is flat; burn rises with fee income. Beyond some level of use, burn exceeds issuance and net supply contracts. This page does not forecast that level; it commits to publishing the two numbers that decide it.
6. What KOVO is not
KOVO is not the access mechanism: grants are. It is not the unit of payment: fees are paid in USD stablecoin. It is not a claim on any institution's data or on any Pool's proceeds. Two instruments are deliberately kept separate from it. Kovo Shares are per-Pool rights in a Collective's governance and proceeds. Kovo Forward is a per-Pool financing instrument, denominated in USD, repaid from a defined slice of that Pool's proceeds at a defined priority. Keeping them per Pool means a failed Pool cannot impair the asset, and the asset cannot be read as a claim on data.
7. Parameters
| Parameter | Value (proposed, 15 October 2026) |
| Result release fee | USD 0.05 per scope released |
| Room run · Market settlement · Forward origination | 5% of compute · 2% of sale · 1% of amount financed |
| Fee allocation | Operators 60% · buyback and burn 20% · treasury 20% |
| Operator commission (default) | 10%; key and release services paid as a separate service fee |
| Bonding period | 7 days |
| Supply cap | 100,000,000 KOVO |
| Operator issuance | 15% of cap over ten years, flat |
| Ledger | Permissioned BFT; validators: C² Labs, institutions, audited custodians |
| Settlement | USD stablecoin for fees; KOVO for Ledger operations |
| Governance | Maintainer role (C² Labs) with an operator council veto; holder governance is a target state |