Token Dust

Overview

Token Dust is a very small token balance or transfer amount that is technically valid but economically impractical to spend, consolidate, account for, or display. Dust can arise from rounding, fees, rewards, partial fills, rebasing, or unsolicited transfers. 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.

Dust is context-dependent: the same amount may be usable on a low-fee network and uneconomic on a high-fee network. It should be read alongside Token Dust Threshold, Token Minimum Transfer, 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, systems need policies for minimum credit, display, sweeping, refund, donation, write-off, and accounting treatment while retaining exact on-chain evidence. 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 attackers can send dust for address tracing, spam, poisoning, or operational disruption, and careless aggregation can create privacy or fee problems. 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.