Quote from: Bude Stacks on Today at 01:33:57 AM

Back on the x vs z pubs. On Trezor, when I show the "xpub" to scan, the typed version starts with "tr([db373be9/86'/0'/0']xpub........../<0;1>/*)" tr presumably means taproot, no idea what the db###be# stands for, then it has the 86' derivation path start. It's so weird that BlueWallet would show it as an m/44' unless it translated it into something different.

One stranger, the ...... in quotes above matchs on the Trezor and BlueWallet. The difference is BlueWallet doesnt have the other stuff in quotes.

The quoted part is called "descriptor", the "db373be9" is just the master fingerprint and not too important.

It's probably because those wallets don't support descriptors and somehow imported the xpub, but I don't have a Trezor to confirm it.

You can try Sparrow wallet which supports hardware wallets and descriptors. (from Bitcoin.org wallet list)
Things you can try:

When creating the wallet, select "Legacy" script type but edit the Descriptor to match the xpub of your trezor's Taproot account.
Or create another wallet, select Taproot but leave the descriptor intact.