Token Base Unit

Overview

Token Base Unit is the indivisible integer unit recorded by a token contract or ledger. User-facing token amounts are usually derived by scaling this integer according to the token’s decimal setting. 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 is a machine accounting unit, whereas a display unit is the human-readable quantity shown in wallets and applications. It should be read alongside Token Decimals, Token Minimum Unit, and Token Display Unit. 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, systems must store and transfer integer base units, retrieve the verified decimal value from the correct token contract or registry, and apply explicit rounding when converting to display amounts. 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 using floating-point arithmetic or the wrong decimal setting can create severe payment, balance, pricing, and reconciliation errors. 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.