Web3 has a simple semantic problem: the same ticker may refer to different assets depending on the chain. The result is confusion, wasted fees, and reduced trust. We propose a minimal, voluntary, and open convention to make interfaces clearer.

DustEthic proposal

Minimal standard - format: @
  • ETH@mainnet - Ether on Ethereum mainnet
  • ETH@bsc - Ether represented on BNB Smart Chain
  • USDC@circle - USDC issued by Circle on officially supported chains
  • USDC@hyper - Local USDC on HyperEVM

Naming rules

  1. @mainnet for the canonical asset of its origin chain.
  2. @circle, @tether, etc. for official stablecoin issuers.
  3. For local or unofficial bridges use the short chain alias: @bsc, @polygon, @arbitrum, @hyper.
  4. UI: keep the short ticker, but display the suffix next to the name and in confirmations.

UI examples

TickerNetwork
USDC@circleEthereum
USDC@polygonPolygon PoS
USDC@hyperHyperEVM (local)
ETH@mainnetEthereum
ETH@bscBNB Smart Chain

Progressive adoption

  • Wallets: show the @... suffix in asset lists and signing screens.
  • Relayers and aggregators: include the suffix in swap routes and confirmations.
  • Explorers: expose a simple namespace field in token metadata.

Goal

Reduce confusion without introducing a central authority. A voluntary convention already improves UX and safety.

License

Open specification under the MIT license. Reuse and forks are welcome.

0
Would love your thoughts, please comment.x
()
x