Token Dust Threshold

Overview

Token Dust Threshold is the configured amount below which a token balance or transfer is classified as dust for a particular wallet, exchange, payment system, or network. 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 an operational policy threshold, not necessarily a universal protocol rule or the token’s minimum unit. It should be read alongside Token Dust, Token Minimum Transfer, and Token Decimal Precision. 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, the threshold should account for network fees, token price, minimum transfer rules, sweep costs, precision, customer impact, and changes in market conditions. 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 a static or poorly disclosed threshold can strand customer funds, reject legitimate small payments, or create inconsistent accounting across products. 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.