Hello i don’t see my funds in hidden wallet trezor suite (btc)
I’ve created an hidden wallet last week. send btc from standard to hidden. now i want to check if the transaction came trough. keeps mentioning that the hidden wallet is empty. the transaction is final in the standard wallet.
-thinking i’ve made a typo by creating the passphrase is tried numerous variations without any luck yet.
-i’ve checked (in the standardwallet) the btcaddress where the btc is send with Bitquery, there is shows empty with no transaction.
I’m very confused and nervous right now. Any suggestions what to do?
update: looking it up in mempool.space the recipient address does show the funds
so it just keep on trying the passphrase? very sure what it should be, can only be a typo, any tools for this?
I’m sorry to read that you cannot see your funds. From your description, it looks like you are in a different wallet. A different wallet can be accessed if you have a different recovery seed in your Trezor or you use a different passphrase.
Generally, when the same recovery seed is used and the same passphrase is entered, the same wallet (with the same set of addresses) is accessed. There is no exception, the public-key cryptography ensures it generates always the same result even when using different interfaces (such as Trezor Suite, MEW, MetaMask, Exodus…)
In case you have the right recovery seed (which is stored in your Trezor device), the passphrase is the only option how you can create a different wallet within this one recovery seed. Every passphrase creates a unique wallet then (1 unique passphrase = 1 wallet). Please remember that passphrase can be any word or any set of letters (in ASCII format and with 50 characters max), it is case sensitive, and empty space is also a valid character, please also think of a different keyboard layout you could have used.
There is a simple way how to verify you use the right recovery seed. Please check that the recovery seed stored in your Trezor device matches your recovery seed backup (the one you created when initialized your device for the first time). You can find instructions on how to perform this check here:
for Trezor Model One: https://trezor.io/learn/a/test-recovery-seed-on-trezor-model-one
for Trezor Model T: https://trezor.io/learn/a/test-recovery-seed-on-trezor-model-t
for Trezor Safe 3: https://trezor.io/learn/a/check-backup-on-trezor-safe-3
In case recovery seed in your device matches your recovery seed backup, the only way how to access a different wallet (with different addresses) is with a different passphrase.
Thanks for the elaborated reply.
I was able to verify the seedphrase and this still the same and correct one which i started this Trezor One with.
Is there is way that I can check that the address which the BTC is currently on is connected to my seedphrase? That I didn’t make mistake in the receiving address. So I know 100% sure thats just the passphrase thats ‘missing/incorrect’.
Other question. When I generated the receiving BTC address in the hidden wallet it stays with this wallet(seedphrase+passphrase) forever, correct? Also when it’s not used.
Thanks in advance.
Is there is way that I can check that the address which the BTC is currently on is connected to my seedphrase?
Unfortunately not if the address is generated from the hidden wallet. The only chance how to access the hidden wallet again (and see if the used address is part of this hidden wallet) is by entering the correct passphrase.
When I generated the receiving BTC address in the hidden wallet it stays with this wallet(seedphrase+passphrase) forever, correct? Also when it’s not used.
I can confirm that this address is cryptographically generated from the combination of recovery seed and passphrase that you used. If you will enter the same wallet (the same seed stored in Trezor and the same passphrase entered), it will always include the same address.
Generally, when the same recovery seed is used and the same passphrase is entered, the same wallet (with the same addresses generated in the same order) is accessed. There is no exception, the public-key cryptography ensures it generates always the same result.