INT utility
4.27 Utility surface
INT carries six functions inside the Yumo Yumo protocol. Two are live; four are planned and activate as the protocol surface matures.
| Function | Status | Description |
|---|---|---|
| Reward asset | Live | Users earn INT through the bINT → INT conversion lifecycle (4.4) for verified Proof of Expense contributions |
| Staking asset | Live at TGE+1 week | Holders lock INT into tier-weighted staking pools (4.6) to earn rewards from the staking incentive allocation |
| Buy-back-and-burn target | Live at revenue onset | Treasury uses data-product revenue to buy INT on the open market and burn it (4.9), creating deflationary pressure |
| Data report burn | Planned | Businesses accessing aggregated community data reports must burn a designated amount of INT per report (4.30) |
| Governance signal | Planned | INT-weighted signaling for decisions over data-product priorities, treasury allocations, and ecosystem grants |
| Bonded API access | Planned | API consumers of the anonymized data product may be required to bond INT against their access keys |
4.28 Real yield
INT is designed as a real-yield asset. Its long-term value capture comes from external revenue generated by the data-product business, not from token emission.
Two mechanisms connect platform revenue to token holders:
- Staker yield. A portion of net data-product revenue flows into a staker yield pool, claimable by INT stakers proportional to their stake and tier weight.
- Buy-back-and-burn. A portion of net revenue is used by the treasury to buy INT on the open market and permanently burn it.
The split between staker yield and buy-back-and-burn is a treasury policy parameter, governed under the controls described in 4.10. Both flows are tied to external revenue, not to token emission. This separation means that emission (4.19) expands supply predictably while real yield compresses or distributes supply based on actual business performance.
4.29 Revenue sources
Revenue that feeds the real-yield mechanism comes from:
- Anonymized data sales. k-anonymized, aggregated receipt-level data sold to FMCG brands, retailers, research firms, and developers through tiered API access.
- Affiliate and referral revenue. Price-comparison click-throughs to retailer or coupon partners (planned).
- Premium subscription. Advanced personal analytics and goal automation features (planned).
Revenue generation details and anonymization architecture are described in 05 Data Schema and API.
4.30 Data report burn
Businesses that purchase aggregated community data reports are required to burn a designated amount of INT for each report they generate. The burn happens on-chain and is permanent.
This mechanism serves two purposes:
- Deflationary pressure. Each data report consumed permanently removes INT from circulating supply, creating demand-side scarcity proportional to the data product's commercial adoption.
- Value alignment. The burn requirement ties the utility of the data product directly to the token. As more businesses consume Yumo Yumo data, more INT is removed from circulation, strengthening the relationship between platform usage and token value.
The burn amount per report is set by treasury policy and varies by report tier (e.g. category-level aggregates vs. full basket-level panels). The pricing structure ensures that the burn cost remains a small fraction of the data product's commercial value while generating meaningful cumulative impact on supply.