Ethereum Spam Tokens, Dust Attacks & Address Poisoning: Anti-Spam Stack Explained

A new analysis argues Ethereum and other chains can’t fully “ban” spam tokens because public blockchains allow anyone to send assets to public addresses. Instead, it focuses on making spam costly and less effective. The article explains three related but distinct threats: spam tokens (unsolicited token transfers to lure users), address poisoning (zero/low-value transfers to an address that visually resembles a victim’s used address), and dusting behaviors (often mislabelled on account-based chains). It says cheaper blockspace and lower-cost execution made nuisance activity easier to scale, so scammers rely less on high conversion rates. Proposed fixes span protocol and user layers. At the protocol level, it calls for stronger repricing of state growth and long-lived garbage (e.g., state/history expiry) to reduce incentives to leave permanent clutter. It also argues for economic separation so mass unsolicited “spraying” costs more than normal transfers, plus token standard upgrades such as clearer metadata rules, issuer attestations, and opt-in display models. For faster deployment, the biggest gains are in wallets and explorers: hide unknown tokens and unsolicited collectibles by default (quarantine, not deletion), stop treating transaction history like a trusted address book, and improve defensive display design so users can’t easily copy poisoned addresses. Exchanges and custodians are encouraged to make withdrawals to allowlisted/saved destinations the default. The piece ends with practical user steps: don’t copy addresses from history, verify recipients (beyond first/last characters), ignore unsolicited tokens, and send test amounts for larger transfers. It notes the same anti-spam requirements apply across low-fee chains, not just Ethereum.