• © Goverland Inc. 2026
  • Privacy Policy
  • Terms of Use
Trust WalletTrust Walletby0x5b05bF7c49709d410077cc12F4d4914F1755AccE0x5b05…AccE

Dust clean-up of Binance exchange addresses on both chains (bep2 and bep20)

Voting ended over 3 years agoSucceeded

Proposal Title Dust clean-up of Binance exchange addresses on both chains (bep2 and bep20)

Proposal Introduction Welcome to the next governance opportunity for Trust Wallet users and TWT holders! Here you can vote on whether the Trust Wallet and Binance teams should clean up the exchange addresses which are currently holding dust amounts of TWT to show more transparency and prudence for the community. We propose to scrape all the Binance-controlled user exchange addresses periodically (once a month) and collect all this dust (even addresses holding 0.000000000000000001 twt) to a single Binance Hot Wallet.

Proposal Request To be a pioneer in providing true information about own token holders.

Proposal Details Here is how CeFi and DeFi platforms interact: — If you want to deposit assets from your non-custodial wallet (DeFi) to your exchange account (CeFi), Binance generates a unique address tied to your account. — If Binance wants to have more of this asset to meet its own needs, it ‘sponges’ tokens from depositing addresses to its hot wallet. — If you want to withdraw assets from your exchange account (CeFi) to your non-custodial wallet (DeFi), the withdrawal comes from the Binance hot wallet address (not from your Binance deposit address).

https://docs.google.com/presentation/d/1kTTv0seJkhV3l9_bgKctUOXbrj1iNRV-70WDOZc9tE0/edit#slide=id.p

And here we are facing an issue: once deposited on the exchange, sold and converted to BNB, a small amount of TWT still stays on the users exchange addresses which are controlled by Binance. Here is the list of the Top-100 k addresses holding TWT on the bep20 chain: https://docs.google.com/spreadsheets/d/1H42Y8uX8xzsKUlzXVeIEu3VKcrH8nwLUiuSKZJlE8p4/edit#gid=937281263 We can see that even amongst the Top-100k token holder addresses (out of almost 300 k addresses) possess less than 1 TWT. And a huge part of them are the Binance deposit addresses. So we can assume that more than 50% of TWT-holding addresses which belong to Binance hold less than 1 TWT which have been stuck there for a few years. This dust is under Binance control, but the exchange has never touched the addresses which hold less than 1000 TWT. The situation is the same on the bep2 chain: there are almost 60 k TWT holders, and a lot of them possess a dust of TWT on their exchange addresses. So the number of the token holder addresses has been increasing over time on both explorers. But in reality the amount of tokens no longer belongs to the Binance users, they belong to Binance itself.

Proposal Motivation Trust Wallet is fortunate to be a part of the Binance ecosystem. Thus, from time to time Binance has cleared up its exchange addresses holding >1k TWT. According to the bep20 explorer analysis, over the past 12 months this action was only made five times, but concerning solely the exchange addresses with more than 1k TWT. As a result, both explorers are showing insanely wrong numbers of TWT holders now. Unfortunately, it allows fraudsters to speculate, which creates difficulties for regular users to count real TWT holders. It just doesn’t reflect reality. Our goal is to clean up all these exchange addresses (with less than 1k TWT in possession) — to provide trustworthy and reliable information. This move seems easy and simple to do periodically, perhaps on a monthly basis.

Benefits for TWT Holders We know there are thousands of TWT holders. And we want to know how many of us are actually there.

Benefits for Trust Wallet One more step to build confidence.

Benefits for Binance More tokens in direct possession.

Useful Links TWT on bep20: https://bscscan.com/token/0x4b0f1812e5df2a09796481ff14017e6005508003#balances TWT on bep2: https://explorer.bnbchain.org/asset/holders/TWT-8C2

Off-Chain Vote

Yes
7.98M TWT94.8%
No
441.44K TWT5.2%
Download mobile app to vote

Timeline

Aug 04, 2022Proposal created
Aug 04, 2022Proposal vote started
Aug 11, 2022Proposal vote ended
Oct 26, 2023Proposal updated