For reaching out and sharing the screenshot highlighting the new error you encountered with your Trezor T following a Factory Reset. We appreciate your efforts in attempting a reset and informing us about the resulting issue. Your detailed reports have been invaluable so far and have been passed on to our development team, who are currently investigating the matter.
Your active participation and diligence in our community are greatly appreciated.
Weāve noted the āDiscovery Errorā related to Solana accounts and understand how this can be concerning. Our development team is currently investigating this as a potential backend issue. While weāre equally eager for a resolution, these investigations can take some time, especially with the complexities involved in blockchain technologies.
We appreciate your patience in this matter. Our support team is actively monitoring the situation and incorporating all new information into our investigation. We assure you that we are working diligently to find a solution, despite the upcoming Christmas period. Your understanding and patience during this busy season are greatly appreciated.
We will keep you updated with any developments as soon as we have more information. Rest assured, we are committed to resolving this issue promptly and efficiently.
Thank you again for your patience and for being a valued member of our community.
Just wanted to drop a quick note to say sorry for not getting to your ticket yet. Weāre a bit swamped, but donāt worry, we havenāt forgotten about you! Weāre doing our best to catch up, and your issue is definitely in the queue. Thanks for your patience ā we really appreciate it. Weāll get back to you as soon as we can.
Hey I appreciate your reply. Iām less concerned with the issue than someone reassuring progress. So this is helpful and Iām happy to be patient.
One question I have though is regarding your comment about it being a āpotentialā backend issue.
What I am looking for is assurance that our funds will be recoverable once you find out what the issue is and they are not unrecoverable despite it being a potential backend issue or otherwise.
If you can assure me of this it would greatly help me to rest a bit more at peace as this investigation is ongoing.
I totally get your concern regarding the term ābackend issueā and the safety of your funds. Let me share my thoughts based on experience, though keep in mind this is more speculation than confirmation.
When we talk about a ābackend issue,ā it usually refers to challenges with the Trezor Suiteās connection and synchronization with the Solana blockchain. This means there might be a hiccup in how your account data is fetched and displayed, but it doesnāt directly impact your actual funds on the blockchain. If you see your transactions on a Solana explorer, it strongly suggests your funds are safe and intact.
Based on similar cases, these issues often get resolved with the suite re-aligning its display to accurately reflect the blockchain data. However, I canāt give a definitive guarantee ā itās more about what weāve seen in past discovery issues.
Weāre on this and will update you with concrete information as soon as we have it. Your patience in the meantime is much appreciated.
I canāt provide an answer to your question about recovering the wallet in Phantom using the Trezor seed. However, Iāll make sure to pass this query along to our dev team for further insights.
As we continue to investigate the Solana issue, understanding more about your specific setups could really help us. If you could share the platform (Windows, MacOS, Linux, etc.) and the versions of any relevant software (like browsers and Trezor Suite) youāre using, it would be incredibly helpful. Preferably via an offical support ticket.
Itās possible that this issue might be related to certain configurations or software versions, so your details could be crucial in identifying a pattern or a cause.
Thanks so much for your cooperation and patience so far.
I have been a huge advocate of trezor for years but this was absolutely unacceptable. You guys announced support for an asset and then had pretty terrible support for this issue. This is the only place Iāve been able to get a reply hours later and the guidance was āyour assets SHOULD be safe, but we cant guarantee itā and āwe are working on fixing it but it will just take a whileā
For anyone else stressing about this, 12 word phrase works to restore for SOL and SPL to Phantom. I recommend transferring out after you do this though.
After looking at this thread SOL must be a new addition for trezor.
I just got my trezor T, tried to recover a ledger seed on it. At first it worked and all my assets showed up, but then I sent some more SOL to it, and all the original SOL just disappeared, only the new transaction shows up.
Looking at the ledger the new transaction is not showing up at all on it. This tells me trezor has really screwed something up. Iām scared to do anything with other assets on it now if it is this unstable.
Solana is indeed a new addition for Trezor The issue isnāt with the device. Itās with the Trezor Suite software syncing with the Solana network so that it can read what assets you have stored on it. Itās only specific to Solana. No other assets are impacted. If you restore that same seed phrase on any other device it will be able to interact with your Solana assets. If you pull up your Solana address on the blockchain explorer, you will see that your assets are all there. Iām not part of the team, but I can tell you that from a technical standpoint, nothing is āscrewed upā. They simply need to get their Trezor Suite software able to pull data from the Solana network correctly.
When I enabled Solana on my model T the bitcoin on a different wallet in trezor suite fails to load transaction history for the bitcoin wallet.
It seems like SOL is glitching not just SOL but also bitcoin transaction history.
When I tried to reset the trezor app my the bitcoin wallet said Asset not loaded correctly for Bitcoin. I finally was able to fix this by disabling the Solana coin from my other wallet.
It feels like it is more than just a sync issue. If it were just a sync issue then I would have expected the test sol I sent to the T to also show up on my Nano since they are both using the same seed, however it did not.
Itās possible that since the T used a new address that the Nano simply isnāt scanning that address due to a cached address list or something, and once the T is working correctly iāll explore that idea.