Token Standard
What the x/tokenization module is, how its pieces fit together, and the order to read this tab in.
x/tokenization is the Cosmos SDK module that defines BitBadges tokens. Read this tab if you build against the chain directly or need to understand the rules an application enforces on your behalf.
What the Module Does
A collection is an on-chain object that holds tokens with numeric IDs. Every transfer of those tokens runs through an approval engine that checks three layers of rules: the collection's rules, the sender's rules, and the recipient's rules. The manager configures the collection's rules and locks them with permissions. Nothing runs in a smart contract; the module enforces every rule on every transfer.
bb query tokenization get-collection 1Main properties:
- No code and no smart contracts. Everything is module state and Cosmos messages.
- Three approval levels (collection, outgoing, incoming) that a transfer must satisfy.
- Approval criteria that gate transfers on payments, proofs, votes, token ownership, dynamic stores, EVM queries, and time.
- Any IBC coin can be attached to a transfer as a payment.
- Tokens can be wrapped into
x/bankdenoms for IBC and for the DEX. - Extendable with the EVM precompiles and the extension hooks.
Module Map
| Area | What it covers | Read when |
|---|---|---|
| Concepts | The data model: ranges, balances, collections, address lists, approvals, permissions | First. Everything else assumes it. |
| Approval Criteria | Every field of approvalCriteria and how each one is enforced | Designing transferability |
| Messages | One page per transaction message | Building a transaction |
| Queries | One page per query | Reading chain state |
| IBC and wrapping | Alias denoms, wrapper paths, backed minting, transfer hooks | Moving tokens across chains or into the DEX |
| Integrate | Standards, extension hooks, ante handler gates | Extending the chain itself |
| BB-402 | Payment-required protocol built on approvals | Charging for access |
| Chain tab | The other modules (x/gamm, x/managersplitter, ...), EVM precompiles, endpoints, nodes | Anything about the chain around the module |
Reading Order
- Concepts, in the order that page lists.
- Approval Criteria once you know what an approval is.
- Messages and Queries as reference while you build.
Most application developers do not need this tab. The BitBadges API returns balances and metadata, and the bb CLI and MCP builder tools generate valid transactions without hand-writing the structures described here.