Token Granularity

Overview

Meaning and scope

Token Granularity is the smallest meaningful increment in which a token can be represented, transferred, priced, settled, or accounted for within a specific system. It reflects both ledger divisibility and application-level rules. Granularity can be coarser than the contract’s minimum unit when exchanges, payment products, or legal instruments permit only larger increments.

How it works

Operationally, teams should define granularity separately for balances, orders, transfers, fees, redemptions, and reporting and should align rounding across all connected systems. The principal risks are that mismatched granularity can create rejected transactions, residual balances, unfair rounding, and discrepancies between on-chain and financial records.

Operational checks and limits

Granularity describes the finest usable increment determined by token precision or other transfer rules. Display rounding must not silently force an amount that the token cannot represent.

Practical example

An invoice tries to request 0.0000001 units of a token with only six decimals; the application must reject or explicitly round the quantity.

Distinctions

Granularity describes allowed increments; base units are the actual integer accounting representation behind those increments.

How to evaluate it

Display metadata is convenient for people but cannot establish the identity or amount of an asset on its own; when processing Token Granularity, a wallet or merchant system should bind the value to a network, a contract or native-asset identifier, and the unit precision used for arithmetic. When evaluating Token Granularity, a misleading label or icon must not redirect a payment to a different asset or alter the recorded invoice amount. Related concepts: Token Minimum Unit; Token Decimal Precision; Token Minimum Transfer.