What dust actually is
Every blockchain charges a network fee to process a transaction, and that fee does not scale down to zero — it has a floor set by the chain and its congestion. Dust is any balance that falls below the point where moving it makes economic sense: if it would cost more in gas to send a balance than the balance contains, that balance is effectively stranded. The coins are still yours and still real, but spending them would leave you with less than you started with, so in practice they stay put.
Dust accumulates as a natural byproduct of normal activity. When a wallet sends part of its balance, the remainder it keeps can be a small, awkward amount; over many transactions those remainders pile up. On chains that model balances as discrete unspent outputs — Bitcoin among them — dust is especially visible, because each tiny output has to be spent individually and each one carries its own share of the fee. On account-based chains the same idea appears as a balance too small to withdraw without the fee eating all of it.
Some networks formalize the idea with a "dust limit" or a minimum-balance rule: a transaction output below a set threshold is rejected as uneconomical, and an account may be required to hold a small reserve to stay open. These rules exist to stop the ledger from filling up with balances that can never realistically be moved. The exact threshold differs from chain to chain, which is part of why what counts as dust on a high-fee network is perfectly spendable on a low-fee one.
Why dust matters in a crypto payment
For a business taking crypto, dust shows up most often as a tiny remainder rather than a problem with any single payment. A balance can be left holding amounts too small to sweep economically — the value is real but moving it would cost more than it is worth, so it sits. The size of that threshold depends entirely on the chain: the same leftover amount is trivial dust on a high-fee network and an ordinary, spendable balance on a low-fee one like Tron or Solana.
Dust also has a security angle worth knowing about. A "dusting attack" is when someone sends a small, unsolicited amount of crypto to many addresses, then watches the blockchain to see how those tiny balances are later combined or moved, trying to link addresses to a single owner and de-anonymize them. The dust itself is harmless to receive; the risk is in carelessly consolidating it with other funds. It is a reason to treat an unexpected small inbound amount with mild suspicion rather than as free money.
Because dust is a consequence of network fees, it is closely tied to which chain a payment travels over. The same logic that makes low-fee networks attractive for small everyday transfers also means they rarely produce dust that matters: when the fee to move a balance is negligible, almost no balance is too small to spend. High-fee chains raise the threshold, so more of what they leave behind ends up stranded.
- Defined by fees, not by the coin — dust is ordinary value that has become too small to move economically.
- Chain-dependent — what is dust on a high-fee network is spendable on a low-fee one.
- Accumulates as remainders — the small leftovers of past transactions pile up over time.
- Watch dusting attacks — unsolicited tiny inbound amounts can be a privacy-probing tactic, not a gift.
Dust on halfin
halfin anchors invoices to a fiat amount and maps that figure to the payable amount in the chosen asset using the live rate, locking it when the invoice activates. The payer sends that amount and pays the network's gas fee separately, so dust is rarely something a merchant has to think about per payment — the invoiced figure is the figure that is settled, regardless of the tiny remainders moving around in the payer's own wallet.
Where dust is worth keeping in mind is on the edges. A network's gas fee is a real cost on every transfer, including money leaving the platform through a single payout or a mass payout, so a destination amount that is itself near the dust threshold may not be economical to send on a high-fee chain. And the same fee mechanics that create dust are what occasionally cause a deposit to land slightly under the invoiced amount — when a payer's wallet takes the fee out of the amount sent. halfin treats that as an underpaid invoice and surfaces it explicitly rather than absorbing the shortfall silently.
If you receive a small, unexpected inbound amount you did not invoice for, the prudent reading is a dusting attempt rather than a windfall. It does not compromise your funds on its own, but it is a reason to be deliberate about how balances are combined, and to lean on halfin's audit trail to keep what arrived and why clearly separated from your real settlement flow.