Trust Wallet just got lighter. The self-custody app says it has removed nine years of accumulated code, shrinking the app by 200 MB.
The company isn’t done, either. More code cuts are planned, which suggests this is the opening act of a longer cleanup, not a one-off spring clean.
What Trust Wallet actually removed
The October 19, 2026 announcement covered legacy code, outdated technology stacks and unnecessary dependencies. Those three categories add up to roughly 200 MB of reclaimed space.
Trust Wallet describes the work as “behind-the-scenes” refactoring. Refactoring means restructuring existing code without changing what the app does for the user. The wallet should behave the same. It just carries less baggage under the hood.
CEO Felix Fan pointed to further optimizations aimed at performance and efficiency. He also offered a memorable description of what it’s like to rework a live product used by millions.
“Making jet engine changes in-flight.”
For reference, around mid-October 2026, before the optimization work, the Android version of the app sat at about 160 MB. The iOS version was around 250 MB.
The second round of trimming this fall
The code purge is not happening in isolation. On September 15, 2026, Trust Wallet dropped native support for 25 lower-activity blockchain networks.
The stated goal was to let the company focus its engineering resources more tightly. Fewer networks to maintain means fewer integrations to update, test and secure.
Crucially, users on those networks were not locked out of their funds. Assets stay accessible through recovery phrases, the string of words that acts as the master key to a self-custody wallet.
Nine years of technical debt
Trust Wallet has a long history by crypto standards. Binance acquired it in 2018, and it has kept growing since.
The app now supports over 100 blockchains. It also claims more than 200 million downloads, a user base that makes any structural change high stakes.
What this means for users and the wallet market
For everyday users, the most obvious benefit is practical. A smaller app takes up less storage and could load and update faster, which matters on older phones or devices with limited space.
The security angle may be the more important one. In general, less code means fewer places for bugs to hide. Security researchers call this the attack surface, the total set of entry points an attacker could probe. Every outdated dependency is a potential weak link, and removing unused ones could reduce risk without users lifting a finger.
The trade-off showed up in September. Users of the 25 dropped networks lost native support and had to rely on recovery phrases if they wanted continued access through other tools.
What to watch next is the follow-through. Fan has flagged more optimizations, and the company has promised further code cuts.
Disclosure: This article was edited by Kaye Quema. For more information on how we create and review content, see our Editorial Policy.