Dusk and RWAs: what the wallet data actually shows
The thing that stopped me mid-scroll: Binance's Ethereum hot wallet holds barely 1.5% of the legacy ERC-20 DUSK supply. As of Aug 13, 2026, Etherscan showed that address sitting on 7.54M DUSK about $460K at $0.0611 out of a 500M-token supply spread across 19,763 holders. For a token whose entire pitch is regulated institutional flow, that's a thin CEX footprint on the bridge contract.
I went digging expecting the opposite: a fat exchange balance parked on the bridge token, the way you'd see with most alts. Instead most of the real supply logic now lives on native mainnet (launched Jan 2025), where these EVM-side legacy tokens are increasingly just migration remnants, not where activity happens. The BEP-20 side told a similar story comparable price, comparable order-of-magnitude holder count, no dominant whale sitting on the contract.
What this tells us: legacy bridge-token balances aren't a reliable proxy for exchange exposure or user activity anymore once a project has its own chain live. What it doesn't tell us: I can't see native DUSK balances held by Binance directly, since that ledger isn't EVM-readable through these explorers, so total exchange exposure is still a blind spot.
If you're tracking DUSK for the NPEX/RWA angle, are you weighting native-chain data or still checking the bridge contracts out of habit?
@Dusk_Foundation $DUSK #dusk
The thing that stopped me mid-scroll: Binance's Ethereum hot wallet holds barely 1.5% of the legacy ERC-20 DUSK supply. As of Aug 13, 2026, Etherscan showed that address sitting on 7.54M DUSK about $460K at $0.0611 out of a 500M-token supply spread across 19,763 holders. For a token whose entire pitch is regulated institutional flow, that's a thin CEX footprint on the bridge contract.
I went digging expecting the opposite: a fat exchange balance parked on the bridge token, the way you'd see with most alts. Instead most of the real supply logic now lives on native mainnet (launched Jan 2025), where these EVM-side legacy tokens are increasingly just migration remnants, not where activity happens. The BEP-20 side told a similar story comparable price, comparable order-of-magnitude holder count, no dominant whale sitting on the contract.
What this tells us: legacy bridge-token balances aren't a reliable proxy for exchange exposure or user activity anymore once a project has its own chain live. What it doesn't tell us: I can't see native DUSK balances held by Binance directly, since that ledger isn't EVM-readable through these explorers, so total exchange exposure is still a blind spot.
If you're tracking DUSK for the NPEX/RWA angle, are you weighting native-chain data or still checking the bridge contracts out of habit?
@Dusk_Foundation $DUSK #dusk