Revise path warning

[andrewkozlik]

When a non-standard BIP32 path is used for a particular coin and script type Trezor shows a warning. This usually pops up at the user at the beginning of the workflow and doesn't say much to someone who isn't expecting it. Also, T1 doesn't show the actual path. We should revise the wording and content of the dialog. Suggestions:

1. "Path m/86'/0'/0'/0/0 does not match the selected coin and script type. Continue?"
2. "Unknown path m/86'/0'/0'/0/0 for the selected coin and script type. Continue?"

We should also investigate to make sure the wording makes sense everywhere the dialog is used. For example in some altcoins it might be more like "does not match the selected network".

[matejcik]

I would use "account" or "account type" in place of "script type", because that seems more legible to the end user.

Perhaps something like "wrong address path for selected account" covers Bitcoin and altcoin usecases equally?

[andrewkozlik]

Proposal

[pedromtcosta]

I'm sorry if this is not the right place to ask, but isn't 86' /0' /0' /0 /0 a correct path for taproot?

[andrewkozlik]

I'm sorry if this is not the right place to ask, but isn't 86' /0' /0' /0 /0 a correct path for taproot?

It is correct for Taproot, but it wouldn't be correct if the specified script type was legacy or SegWit v0 for example.

[matejcik]

@Hannsek I believe we have some designs ready for this, no?
i would love to get this done if so

[Hannsek]

We have, I'll post them here. (Waiting for Ben's answer on copy)

[Hannsek]

Here it is:

[Hannsek]

Fixed

Updated screen.

[matejcik]

(Please remove the exclamation mark from "account!". Nowhere else we shout at the user, and there is already a "!" in the icon.)

[Hannsek]

Isn't this done already? @mmilata

[mmilata]

Yes, in #3177.