Token Minimum Unit

Overview

Token Minimum Unit is the smallest quantity of a token that the underlying ledger can represent as one integer base unit. For a token with six decimals, the minimum unit normally equals one millionth of a displayed token. For token integrations, the relevant rule can exist in smart-contract code, an upgradeable module, an issuer policy, or an off-chain compliance service. Systems should therefore inspect both the deployed implementation and the current administrative configuration instead of relying on a token name or interface label.

It defines mathematical divisibility and should not be confused with a minimum transfer, minimum order, or economically useful dust threshold. It should be read alongside Token Base Unit, Token Decimals, and Token Granularity. These related concepts describe different parts of the lifecycle, so substituting one label for another can hide who has authority, which balance is measured, or what action is actually permitted.

Operationally, developers must perform arithmetic in integer units, read the verified decimals setting, and document any application rule that prevents users from using the full protocol-level divisibility. A production system should preserve the applicable network, contract or asset identifier, units and precision, rule version, responsible role, effective timestamp, and the transaction or source record used to make the decision. Changes should be observable and reconciled rather than inferred from a wallet display alone.

The principal risks are that incorrect scaling, overflow, truncation, or floating-point calculations can make the minimum unit disappear or be misvalued in connected systems. Teams should test normal and exceptional paths, including failed transactions, delayed external services, upgrades, role changes, unavailable redemption or transfer routes, and inconsistent data between blockchain, market, legal, and accounting systems.