TrezorConnect.signMessage fails with Taproot address

[bkiac]

Description

When calling TrezorConnect.signMessage({ path: "m/86'/0'/0'/0/0", message: "msg" }) using @trezor/connect-web version 9.4.7 the action fails.

---

Steps to Reproduce

1. Install and import @trezor/connect-web version 9.4.7.
2. Initialize TrezorConnect.
3. Call the TrezorConnect method:

TrezorConnect.signMessage({ path: "m/86'/0'/0'/0/0", message: "msg" });

I know Taproot is not supported by BIP137 message signing so this is probably out of scope for Connect in general, but does Trezor plan to add support for BIP322 message signing?

[mroz22]

thats interesting. could you @Hannsek check if we want to support it?

I quickly tested it and found this #16631 option (not sure if this is the only one).

[Hannsek]

There is still no unified approach how to properly implement taproot message signing, see here.

Until it will be solved, we cannot do anything in Connect.