IO is a composable basket currency denomination on the Heleos blockchain. The IO token represents a weighted basket composed of the chain's tokenized deposit denominations and functions as infrastructure for institutions requiring a single denomination representing diversified exposure to the Heleos tokenized deposit ecosystem.
Architecture
The IO basket is implemented as a composition layer on top of the individual denomination holdings. IO is not independently issued against external collateral. Instead, each IO token represents a claim on a defined basket of underlying IO-family denominations held in the basket's authorized custody address. Minting IO requires deposit of the constituent denominations in the configured basket composition; burning IO releases the constituent denominations to the redeeming address.
Composition
The IO basket is composed of two asset classes at genesis:
| Component | Allocation | Role |
|---|---|---|
| USDIO | 85% | Stability anchor. USDIO is the first denomination with active bank integration through the StableNow platform. As additional denominations achieve live integration and accumulate transaction volume, new components enter the basket by drawing from the USDIO allocation. |
| OS | 15% | Permanent structural component representing the Heleos network's native economic activity and ecosystem participation. The OS allocation is fixed and does not change as the basket composition evolves. |
Composition Logic
- Genesis Composition: 85% USDIO, 15% OS
- Active Integration Addition: When a new denomination achieves live bank integration and begins tokenizing deposits under a partner bank's operational control, that denomination becomes eligible for basket inclusion
- New Component Entry: New components draw their allocation from the USDIO share. The OS allocation remains fixed at 15% regardless of basket expansion
- Weight Assignment: Weights are assigned based on tokenized deposit volume in each denomination, with administrative rebalancing at defined intervals
- Transparent Record: The current composition and the composition history are publicly queryable on-chain
The basket architecture is designed for expansion. As the Heleos ecosystem grows and new asset classes are integrated into the network, the IO basket composition evolves to reflect the full breadth of on-chain economic activity.
Supported Operations
MsgMintBasket- Deposit constituent denominations in basket composition, receive IO (authority or authorized participant)MsgBurnBasket- Return IO, receive constituent denominations per current compositionMsgSend- Transfer IO between Heleos addresses (any holder)QueryBalance- Query IO balance for a given addressQueryTotalSupply- Query total IO in circulationQueryBasketComposition- Query current basket weightsQueryBasketHistory- Query composition change history
Query Endpoints
heleosd query bank balances [address] --denom uioheleosd query bank total-supply --denom uioheleosd query stablecoin basket-compositionGET /cosmos/bank/v1beta1/supply/by_denom?denom=uioGET /heleos/stablecoin/basket/compositioncosmos.bank.v1beta1.Query/SupplyOf with denom uioheleos.stablecoin.Query/BasketCompositionUse Case
The IO basket is designed for institutions that want single-denomination exposure to the Heleos tokenized deposit ecosystem without managing balances across 10+ individual denominations. Use cases include:
- Treasury operations at institutions operating across multiple currency zones
- Cross-border settlement where counterparties prefer a neutral basket over any single sovereign currency
- Diversified deposit products that banks offer to customers seeking multi-currency exposure without individual currency selection
- Reference denomination for smart contracts requiring a stable, composable unit of account across the Heleos ecosystem
As bank integrations expand across jurisdictions, the basket composition evolves to reflect the actual operating geography of the StableNow network.
Technical Documentation - Version 1.0 | Effective Date: April 3, 2026