On March 16, 2024, a technical issue emerged affecting the BEP2 to BEP20 migration feature in the Trust Wallet browser extension. This article provides a transparent and comprehensive update on what occurred, how it was resolved, who may have been affected, and the steps users should take to ensure their assets remain secure.
The issue was isolated to specific versions of the browser extension and did not impact the Trust Wallet mobile app. Immediate action was taken to fix the bug, reimburse affected users, and reinforce development protocols to prevent future incidents.
What Happened During the BEP2 Migration
The BNB Chain team previously announced the deprecation of the BNB Beacon Chain (BEP2), urging users to migrate their assets to the BNB Smart Chain (BEP20) to avoid potential loss. In response, Trust Wallet introduced a migration tool within its browser extension to streamline this process for users.
👉 Discover how secure digital asset management starts with the right tools.
The migration feature was first introduced in browser extension version 2.7.0 and functioned correctly until version 2.9.0. However, updates in versions 2.9.0 and 2.9.1 inadvertently introduced a critical logic error. This bug caused migrated BEP2 assets to be sent to an incorrect destination address—unrelated to the user’s wallet—resulting in fund loss for a small number of users.
Importantly:
- The issue was not caused by a security breach or malicious attack.
- Only the browser extension was affected—not the mobile app.
- Only users who performed migrations using versions 2.9.0 or 2.9.1 before March 17, 2024, at 15:10 UTC may have been impacted.
The bug was promptly reported through Trust Wallet’s bug bounty program, enabling the team to act swiftly.
How the Issue Was Resolved
Upon confirmation of the bug, Trust Wallet’s engineering team implemented immediate corrective measures:
- A warning message was added near the migration button.
- All references to the migration feature were temporarily removed from the interface.
- Transactions on the BNB Beacon Chain were blocked to prevent further losses.
- A patched version (2.9.2) was released on March 17, 2024, removing the faulty migration tool.
- Subsequent versions (2.9.3 and beyond) include the same fix and are fully safe to use.
An updated, thoroughly tested migration tool was reintroduced in version 2.10, released in early April following Chrome Web Store review.
Who Was Affected?
Understanding whether you were impacted is essential for peace of mind and next steps.
âś… You Are Not Affected If:
- You use only the Trust Wallet mobile app.
- You used the browser extension but did not use the migration feature.
- You started using the browser extension with version 2.9.2 or later.
⚠️ You May Be Affected If:
- You used the migration tool in version 2.9.0 or 2.9.1.
- Your transaction completed before March 17, 2024, 15:10 UTC.
- The migrated funds did not arrive in your BEP20 address.
- The original BEP2 balance is also no longer available.
Support for Affected Users
Reimbursement Update – April 8, 2024
All reimbursement payments have now been completed.
Affected users who lost BEP2 assets due to the bug in versions 2.9.0 or 2.9.1 received automatic compensation. Funds were returned directly to the original BEP2 wallet address used during the failed migration—this required no action from users.
In most cases, users were reimbursed with the same type of BEP2 asset they lost. The only exception is ShareToken (SHR), where affected users received an equivalent value in USDT due to technical limitations.
👉 Learn how leading platforms ensure asset safety during blockchain transitions.
Frequently Asked Questions (FAQ)
Is it safe to use the Trust Wallet browser extension now?
Yes. The issue has been fully resolved in versions 2.9.2 and later. The fix was deployed quickly, and no other features were impacted. Both the browser extension and mobile app are secure for everyday use.
How do I check if I’m using a fixed version?
Most browsers auto-update extensions. To confirm:
- Click the puzzle icon (Extensions) in your browser.
- Select “Manage Extensions.”
- Find Trust Wallet and click “Details.”
- Check that your version is 2.9.2 or higher.
If not, restart your browser or manually update.
Was Trust Wallet hacked?
No. This was not a security breach or hack. The issue stemmed from an internal logic error introduced during a routine update—not from external interference or malicious activity.
Will I get back the exact same tokens I lost?
In nearly all cases, yes—users received their original BEP2 assets as reimbursement. Only SHR token holders received USDT equivalent due to smart contract constraints.
How can I safely migrate BEP2 assets now?
You can migrate using the Trust Wallet mobile app, which remains unaffected and fully functional:
- Follow step-by-step instructions in the official BEP2 to BEP20 migration guide.
The browser extension’s migration tool has been reintroduced in a more robust form in version 2.10.
What steps are being taken to prevent future issues?
Trust Wallet takes full responsibility. To improve quality assurance:
- Enhanced testing protocols are now in place before releases.
- The bug bounty program remains active to catch vulnerabilities early.
- Additional code reviews and staging environment checks have been implemented.
Core Keywords
- BEP2 migration
- BEP2 to BEP20
- Trust Wallet browser extension
- BNB Smart Chain
- Asset reimbursement
- Blockchain migration tool
- Web3 wallet security
- BNB Beacon Chain
These keywords reflect user search intent around blockchain transitions, wallet safety, and technical troubleshooting—ensuring this content aligns with SEO best practices while delivering value.
👉 Stay ahead in Web3 with tools built for security and simplicity.
By maintaining transparency, acting swiftly, and prioritizing user protection, Trust Wallet continues to uphold its mission of making digital asset management accessible and secure for everyone. Whether you're migrating tokens or managing your portfolio, choosing reliable platforms is key to navigating blockchain evolution confidently.