User-reward emission

4.3 How rewards flow into bINT

The user-reward pool is governed by the allocation table in 4.17. Inside that pool, daily emission is metered by a curve that takes monthly active usage as its primary input. The curve has three properties worth naming:

• Stepwise growth toward a peak. As MAU grows through defined bands, the daily emission pool expands in steps rather than continuously. This avoids cliff effects when activity oscillates near a threshold.
• Published peak. The daily pool reaches a peak of 12,000,000 INT. After peak, additional MAU raises per-user contribution density.
• Long horizon. The user-reward rail is sized to last a 15-year horizon. The reward share of supply (64.35 billion INT, see 4.17) is the budget; the curve is the meter.

The stepwise function — the MAU bands, the daily-pool values per band, and the transition behaviour — is documented in 4.19. Band boundaries are re-tuned as observed activity evolves.

4.4 The bINT → INT conversion lifecycle

bINT is minted to a user's frozen ATA at the moment a receipt clears the trust layer (03). It then enters a holding period during which the user accumulates conversion eligibility. The lifecycle:

mint  →  hold  →  convert  →  INT in user wallet

• Mint. Per-receipt, into the frozen ATA. The amount is set by the trust band, the user's daily ceiling, and the current emission step.
• Hold. bINT stays in the frozen ATA through a minimum holding window before conversion eligibility. This window makes farming uneconomic: an attacker would have to fund their accounts long enough to reach the window's end, by which point the trust layer has likely already responded.
• Convert. The user invokes the conversion program. The protocol burns the bINT and mints INT at the year-indexed conversion ratio (4.24). The ratio decreases over the horizon; earlier contribution earns more INT per bINT than later contribution.
• Settle. The minted INT lands in the user's standard SPL wallet, transferable.

The minimum holding window length and the per-user conversion rate limit are managed in the internal operations layer.

4.5 Daily ceiling, in tokenomics terms

The effective daily bINT ceiling is the product of a base ceiling, a level multiplier (03 §3.6), and the user's current health (03 §3.5). The current MVP implementation uses per-level tables (4.22); the target architecture uses a formula-based ceiling (4.23). The multiplier and health values are user-specific and live in the trust layer.

This decomposition matters because it lets the protocol re-tune any of the three factors while preserving tokenomics. A market expansion can raise the base; a level system rebalance can shift the multiplier; an abuse wave can compress the health distribution.