rust Wallet Chrome Extension issues after proxy change wallet data lost

Hey guys, I'm reaching out here as a last ditch effort to see if there's any way to recover my wallet, even if it's a long shot. I was using the Trust Wallet extension for Chrome (Manifest v3) in a separate browser profile (not incognito, just a standalone profile). Everything was fine until I switched the proxy settings for that profile. After I changed the proxy, the Trust Wallet extension started showing an "Oops! An error occurred" message and it won't load at all. This issue persists even after I switched back the proxy settings. When I take a look at the Chrome DevTools console, I keep seeing errors like: Cannot convert undefined or null to object Cannot read properties of undefined Errors popping up in functions like getAccountsOfSupportedCoins and registerWallet. This makes me think that the extension's IndexedDB or local storage might be messed up. Some key points: I DON’T have the seed phrase saved anywhere. This wallet was only used in this browser extension, not imported anywhere else. The extension files seem fine (manifest, background.js, wasm files, etc.), but the UI crashes before I can get in. I haven’t uninstalled the extension yet because I want to keep any local data that might be left. I’m not looking to break any encryption or do anything shady. Just asking: 👉 Is there any method out there, whether it's known, experimental, or just theoretical, to: Fix a corrupted state of the Trust Wallet extension, or Force the extension to reindex/reload accounts using the existing encrypted local data, or Regain access if the encrypted storage is still intact but the UI is failing? I get that without the seed phrase, recovery is typically a lost cause. I'm just hoping for any glimmer of a solution.

1. Since you didn't mention anything about customer support, have you tried contacting them for help? 2. If you haven't do it, consider backup all data created Trust Wallet extension. I just tried https://www.w3tutorials.net/blog/chrome-extension-local-storage-how-to-export/ and i can see data for my other browser extension, but i don't know whether this guide also work for Trust wallet extension. FYI Trust Wallet isn't open source. So developer who can help is likely limited to Trust wallet developer, who probably doesn't visit this forum.

I checked the extension storage and it looks similar to how MetaMask stores its "vault data". But this is not for certain since it's a closed-source wallet. If you want to get that data: You can try to export a copy of it from from Chrome's DevTools' Application tab (Refer to ABCbit's link), But instead of going directly to "Storage", browse to "Extension Storage->Local" instead, there, you can get the value of your "trust:vault". It's the value that looks like this (has "data", "iv" and "salt"): But the problem is, although there's an available 'vault decryption tool' made by Metamask, it seem to be using a different encryption. Their open-source Vault Decryptor (GitHub) doesn't work on Trust Wallet's vault data although it's 100% identical. And Trust Wallet's encryption is not documented (or at least I haven't heard of its documentation)

It's too bad that you didn't make at least one backup of your seed phrase when you set up your wallet. Trust Wallet is closed-source, but it's still non-custodial, giving you access to the seeds of your wallets. I assume the same is true for the browser extension as it is for the mobile app. Hopefully, you will learn from this problem and in the future you won't repeat it again and take shortcuts. If you don't manage to recover your wallet, I hope at least that it won't be too expensive of a lesson. I doubt Trust Wallet's customer support can be of much help, but I would still contact them and ask. Tell them about the error messages you see and what you did to cause them. Also, google those error messages to check if there are people who have already reported similar problems. Maybe there is a solution or tip there somewhere on how to fix it.

If you don't have the seed phrase, your only real lifeline is that the encrypted vault is still sitting in the Chrome profile somewhere and the UI is just face-planting before it can render. So treat that browser profile like evidence in a crime show: make a full copy of the whole profile directory first, before you "try one more thing" and Chrome helpfully garbage-collects something. Changing a proxy didn't magically delete keys, but it can absolutely make an extension crash if it expects to fetch coin lists/config and gets a weird network state, and then the front-end throws those "undefined" errors you're seeing.

I don't know why some people are still using the Trust Wallet extension despite the recent incident in which some Trust Wallet users lost $6M+. It was just recent issue last month and maybe this might be the reason why your wallet data or the extension become corrupted. I am using Trust Wallet, but I only use their mobile version to receive airdrops. I think you need some help from Trust Wallet support since the only way that I know to recover your wallet is by using seed backup. If you don't have a seed backup, the chances of recovering your wallet are pretty slim. I did some research and found this one below; it might be helpful, but make sure to make a backup of the extension data folder and make sure to run the decryptor or the extractor offline for safety purposes. Based on the guide provided from that link, it could generate the bip39 seed or extract a base58 private key. Let's see if this one will work on Trust Wallet. - https://www.binance.com/en/square/post/21131027767362