Trezor hidden wallet issue: BTC confirmed on-chain but passphrase not working

Bitcoin client software and version: Trezor Model T running the latest Trezor Suite on desktop. I also checked with Sparrow Wallet in watch-only mode. Operating system: Not applicable (this isn’t a bug with the client software). System hardware specs: Not applicable. Issue description: I sent BTC from Newton (a Canadian exchange) to a self-custody address generated by my Trezor Model T. The BTC is definitely there, confirmed on-chain, and hasn't moved since the transfer. The problem is I can’t access the wallet that created this address. It seems like the address is from a BIP-39 passphrase-protected (hidden) wallet, and I think I'm entering the wrong passphrase. Key points: Only one Trezor device has ever been used. The 12-word recovery seed is correct and verified. If I enter the wrong passphrase, I get a valid but empty wallet, which is what I expect. This isn’t an issue of transaction failure, theft, or anything with the exchange. Related addresses: bc1qgn5raset2n9m0npn50xnyadmlvdgctgdtum3mv Related transaction IDs: Can provide them if necessary, but the address listed shows the confirmed balance on mempool.space. Screenshot of the issue: Not applicable, since there’s no error message; the behavior is just expected when the passphrase is wrong. Log files from the Bitcoin client: Not applicable. What I need: I know that a forgotten passphrase usually can't be "recovered." I’m looking for expert opinions on these points: Are there any remaining derivat...

That is not a valid Bitcoin address. Trezor Suite does not let you load any more accounts if there is already one empty Bitcoin account in the application. If you have already checked different account indexes on Sparrow, then it is most likely that you have the incorrect passphrase for the wallet and will have to use recovery software to brute force it to regain access.

Thanks for pointing this out — you’re absolutely right. This was a transcription error on my part. The correct address is: bc1qgn5raset2n9m0npn50xnyadmlvdgctgdtum3mv The missing q after bc1 in my earlier post made the address invalid when copied. This is a native SegWit (bech32) address, and the balance and confirmations can be verified on mempool.space and other explorers. Apologies for the confusion, and thank you for catching that. The underlying question remains the same: the address exists on-chain with confirmed BTC, but is not derived by the currently opened wallet, strongly indicating a passphrase-protected (hidden) wallet. I appreciate any guidance on remaining derivation-path edge cases worth ruling out beyond passphrase reconstruction.

Post a blockchain link to the address. That address does not show for me. I did three chains all  show zip.

👉 https://blockchair.com/bitcoin/address/bc1qgn5raset2n9m0npn50xnyadmlvdgctgdtum3mv

Since you've used Sparrow, it's possible to select p2wpkh in the script type when creating the Sparrow wallet, then edit a different derivation path when connecting Trezor. So, there's a chance that you might have mismatched the standard derivation path of a certain script type with another. Even non-standard derivation path might have been used. If the issue isn't the passphrase, it's worth trying to reproduce it by mismatching the script type and derivation path when restoring the hidden wallet. Since the address is bc1q..., select "Native SegWit (p2wpkh)" in the script type then change the derivation path in "Show derivation..." to BIP44, 49 or 86 before clicking "import Keystore". Then each derivation path's second, third or higher account_index in case the first isn't used.

So you have an empty address and no way to reproduce it. That makes this whole topic pointless. See post below. For next time: before funding any address, make sure you can reproduce it from scratch by verifying your backup. Also make sure you use the correct address and don't fall for clipboard malware.

They probably meant this address bc1qqn5raset2n9m0npn50xnyadmlvdgctgdtum3mv with 0.7 BTC in it. I don’t blame them for seeking advice, but they should have provided accurate information.

Thanks for the feedback. To avoid further confusion: this address does exist and does contain ~0.7175 BTC, which can be verified here: https://blockchair.com/bitcoin/address/bc1qgn5raset2n9m0npn50xnyadmlvdgctgdtum3mv Some explorers (including mempool.space and blockstream.info) incorrectly reject this address, which is what caused the earlier verification issues. The underlying issue remains unchanged: the funds are confirmed on-chain but are not derived by the currently opened wallet, consistent with either a passphrase (hidden wallet) or derivation-path mismatch. I appreciate the guidance so far.

Before diving into passphrase‑related despair, I would first try scanning addresses a bit deeper that is, beyond the default gap limit of 20 addresses in Sparrow. Open your wallet ==>Settings==>Gap limit==>set it as high as needed==>Watch addresses==> choose All. Then rescan from the date your transaction was sent

You have (literally!) posted the wrong address in all your 4 posts so far. FinneysTrueVision posted an address that looks like it, and is funded. If you would have checked your own link, you would know this. If this is how you handled your passphrase, it's no surprise you can't find back your funds. It sounds like you need to try some variations on your password, or even brute-force it (but not before setting up a secure offline system to run this).

Are you kidding me? Not even blockchair.com accepts this address as valid and mempool.space isn't faulty about the invalidity of above address either (I don't trust blockstream.info). What kind of broken links do you spread or what kind of weird malware do you have on your system, possibly? LoyceV already pointed out that every posted occurence of "your" address is faulty and an invalid Bech32 address. bc1qgn5raset2n9m0npn50xnyadmlvdgctgdtum3mv is invalid because it has a checksum error, see here: Source How about bc1qqn5raset2n9m0npn50xnyadmlvdgctgdtum3mv which holds 0.717509BTC. Seems to be the address you meant. Do you transcript such addresses by hand with possibly poor eyesight (you mistyped a "g" instead of a "q", easy to confuse one for the other)? Why?? Bitcoin public addresses are not supposed to be typed by hand. Too error prone as well demonstrated in this topic. Regarding your issue with the mnemonic passphrase. You should know that any unique mnemonic passphrase derives a completely different and unique wallet. So, the smallest error (e.g. trailing space may count, depending on how the wallet sanitizes the mnemonic passphrase input) gives you an empty wallet. There's brain dead software that includes a trailing space when you select a string to copy/paste it. The mnemonic passphrase can be multiple words, separated by spaces. Not exactly sure if a double space is treated different from a single space. Have to look into the string normalization procedure defined by BIP-39.

You guys are probably having your time wasted by a language model (I'm not saying that OP is a chatbot, I'm just saying that there's very probably a chatbot in the loop here). Let's see... Posting a malformed Bech32 address, then having that mistake pointed out to you, and beginning your response with: "Thanks for pointing this out — you’re absolutely right"? IYKYK And then going on to share the same address along with an (incorrect) explanation of why it was wrong to begin with and why it's now correct (even though, logically, there's no way for that statement to be true)? Yeah, that's AI. (This is very off-topic, but, man I hate this stupid "AI revolution" that some people seem to get really excited about. Every time someone manages to convince me to try the newest/largest models and see how great they've reportedly become, I always end up thinking less of the person who made the recommendation. If you actually try to engage with a language model using subject matter that you're very well versed in, you'll quickly see how incorrect it often is and either how instantly apologetic it then becomes, or how illogical it then reveals itself to be. I think most people find it to be a convincing imitation of intelligence because they engage with it on subjects that they themselves know very little about, and so they can't really tell/see just how confused and simple-minded it is. The last time I tried to chat to one, about something very close to my heart: MS-DOS, the DOS/4GW era of PC gaming, and some of the programming-related arcana of the time, I remember leaning back in my chair afterwards, and thinking, "Huh. That was a very nice simulation of what it might be like to have a protracted back-and-forth with an overconfident and extremely well-read imbecile.")

I reported him in the Ai Spam report Thread but was shut by SatoPrincess who was Supporting his use of Ai For translating. But I didn't know how he/she was that sure about it

Yeah I gave up and decided he was a troll. But bot may be more accurate as to what he is.

I wish non-declared AI tool usage, doesn't matter for what purpose, would be a forum offense treated like plagiarism, leading to permanent ban when found guilty. It's such a waste of time to deal with this shit.