Thank you very much for your comprehensive response and trying to help, I really appreciate it.
If you have multiple coins, and are able to restore all of them correctly with the right seed and passphrase, it is overwhelmingly likely that this is a problem of Yoroi, not of Trezor. Again, we have automated tests confirming that derived addresses do not change between firmware versions. And the fact that other coins did appear indicates that the seed or passphrase is not the issue here.
Yes. Well I am simply using my Trezor and passphrase as normal in e.g. Trezor Suite or Metamask and I can access all my other coins and use them as normal. I never actually had to restore the wallets using my seed, but that should be irrelevant in this case right.
It would be nice to know that you did originally verify your address on Trezor screen, it matched, and now when you try to do the same thing, it also matches (even if it is different from before). If that’s the case, we could be sure that the address is generated by Trezor.
If you originally didn’t do that, there is a distinct possibility that the addresses in your old Yoroi installation didn’t in fact come from Trezor.
When I connect my Trezor via Adalite or Yoroi there is no prompt on the physical Trezor to do anything. What happens is:
- Webpage opens up: TrezorConnect | Trezor Asking for permission to read public keys from Trezor device. I click “Allow once for this session”
- Export multiple Cardano public keys. I click “Export”
- Enter Trezor passphrase. I enter it on my physical device.
That’s it. Then the account is loaded into Yoroi/Adalite. Though when I tried pairing my Trezor with Daedalus I do have to verify the public key on the physical Trezor and click the green checkbox to proceed.
If the address didn’t come from the Trezor, then where could it have come from? Also in Yoroi it does say “Trezor Wallet” with an image of a Trezor next to it, up top, suggesting it is indeed derived from my Trezor.
How many receiving addresses with non-zero balance do you have? Check both the “External” and “Internal” tabs. What are their suffixes?
On the original account with funds on it (that I can’t restore or transact with) there are 2 external addresses with funds on them, and 2 internal. By suffix I assume you mean the end of the derivation path?
External:
m/1852’/1815’/0’/0/2
m/1852’/1815’/0’/0/1
Internal:
m/1852’/1815’/0’/1/1
m/1852’/1815’/0’/1/0
I should also note that when I click verify address to see this, I can see that all these addresses have a respective “Staking key hash” and “Spending key hash”. On the newly derived empty accounts each address only has “Staking key hash”. I don’t know if that is relevant.
Using the same Trezor and only passphrase in Yoroi / Adalite generates empty accounts, as said. I can generate more receive addresses to get more derivation paths. But the ones with the same paths (e.g. m/1852’/1815’/0’/0/2) are still empty and the addresses are different from those in the original account.
Can you use the Export feature to see the old account on e.g. Yoroi Mobile?
Yes, I can use the Export feature in Yoroi and it gives me a QR code which when I scan produces the same original wallet in Yoroi Mobile, with the correct amount of funds.
The public key on my original account (that I can see in Yoroi using Export) is not the same as any of the keys that I see in Adalite when connecting to what should be the same account (same Trezor, same passphrase) but is an empty unused one.
I’m not sure how I can find the Byron/Shelley extended public keys in Yoroi but I suppose this is enough to say that it’s not the same account?
If none of this helps, I’m afraid that you’ll have to turn to Yoroi support again. As I said previously, a nice thing to do would be to get an older version of Yoroi and see if that doesn’t magically fix the problem.
I’ll try to get my hands on an older version of Yoroi and give that a try.
Anyway, with several other users having the same problem with Yoroi and Trezor specifically, and some not even having used a passphrase (no risk of having misspelled something), there has to be a problem somewhere, and a solution too. I’ll see if Yoroi support responds with anything, last time they basically assumed it was a user error (which is not unreasonable to assume, I guess).
Again, thank you very much for your help.