Token classes
4.1 The four classes
Yumo Yumo operates with four on-chain assets, each with a distinct role.
| Class | Form | Transfer model | Role |
|---|---|---|---|
| INT | SPL token on Solana | Market-transferable | Protocol-level coordination, staking, ecosystem incentives. Supply parameters live in the Vision Paper. |
| bINT | Soulbound, held in a frozen Associated Token Account (ATA) | Converts to INT through a defined lifecycle | Contribution accounting layer between work and reward. |
| ePoints | Soulbound, USD-denominated, frozen ATA | In-product insight credit | Record of household-level hidden cost surfaced per verified receipt. |
| Foundation NFT (Yumbie) | User-bound Token-2022 identity asset | Identity asset | Persistent identity. Evolves to the Smart Agent at the milestone defined in the Vision Paper. |
Why four classes
The Vision Paper explains the user-experience reason. The mechanism reason is separation of concerns:
- INT moves through markets and exchanges; it must be transferable and fungible.
- bINT measures contribution intensity and decays in conversion ratio over time; it must be soulbound and time-aware.
- ePoints carry an economic-insight signal as their own record, so user analytics can grow while INT supply remains governed by token mechanics.
- The Foundation NFT carries identity continuity across user surfaces as a user-bound asset.
4.2 Authority structure
Each class has a defined mint authority and, where applicable, a freeze authority. Authorities are held by program-derived addresses (PDAs) controlled by the protocol. The treasury governance layer (described in 4.6) is the operational guardian.
- INT mint authority — program PDA. Mint events are gated by the emission program described in 4.3.
- bINT mint and freeze authority — program PDA. bINT is minted to the user's ATA and frozen in the same instruction.
- ePoints mint and freeze authority — program PDA. Same pattern as bINT.
- Foundation NFT mint authority — program PDA, one-shot per user.
The freeze pattern makes "soulbound" enforceable at the protocol layer rather than relying on social convention. A frozen ATA binds contents to the user's account during the contribution lifecycle; the protocol unfreezes only for the conversion lifecycle in 4.4.