Hey, wanted to share a major issue I noticed with a best practice I was conducting. Note that I did not lose funds but it could have been a close call.
TLDR: I used my seed phrase from the wallet I created with a Trezor Model T and attempted to recover my wallet using Exodus, everything besides my Solana showed up which included, ETH, LINK, BTC. It appeared that my Solana address on my recovery seed was different than the Solana address on my Trezor.
I am making a habit of recovering my wallet on a 3rd party wallet, ensuring that everything transfers over correctly and then doing a factory reset on my Trezor Model T where I will then create a new wallet and then transfer my original balances to this newly created wallet on Trezor. Sure this costed like $10 in network fees but this gives me a sense of assurance that my seed phrase will work on a 3rd party and that my passwords are reset which should make it more secure…even though it probably was 99% secure haha.
So in this process I noticed everything worked successfully other than my Solana balance which appeared as 0. My receive address on exodus and my receive address on Trezor where different but they should have been the exact same as they were both reading off of the same seed phrase. Luckily I was signed into both so I was able to send from Trezor to Exodus. Then proceeded with a factory reset and regenerated a new wallet while successfully transferring back to Trezor.
This is alarming because what if I attempted to recover my seed phrase on a different Trezor Hardware wallet and I had a mismatch of Sol Addresses. Or say Trezor goes out of business and I want/need to use a 3rd party instead. I would basically lose my SOL balance.
I do realize it could be an issue on Exodus’s end but I ask that a developer that reviews the open source code could attempt to look into this issue to ensure it is not Trezor’s mistake.
Also SOL was newly supported on Trezor Model T when I first created my SOL wallet with Trezor. Probably around Jan 2024 so maybe this was a post release bug that was not caught yet.