Pavol Rusnak

Checklist: - [ ] Ed25519 COSI signatures - [x] parse VERSION and FIX_VERSION from the firmware header ([7d93bd3](https://github.com/trezor/trezor-firmware/pull/2270/commits/7d93bd317954144b44e23db2708c22fdbd52dafb)) - [ ] warn when firmware downgrade is happening - [ ]...

I think we don't need to react with "winking" because Trezor is already showing U2F dialog on the display when this happens. This means there is no confusion which device...

The PR is sent against the wrong branch. Superseded by https://github.com/trezor/trezor-firmware/pull/849

I was confused because you opened two PRs. I'll close #849 then and reopen this one.

The current status is that the PR needs to be evaluated but there are things with higher priority in the queue.

Issues marked with the "Product Owner" label need to be evaluated first by the Product Owner and assigned a priority, they are not assigned a milestone before these steps happen....

Is there a BIP standard describing how this should work?

I agree it makes sense to do this, but we need to refactor the `wallet.sign_tx` app first: https://github.com/trezor/trezor-firmware/issues/617

It makes sense to combine this effort with the Taproot support in Trezor. Otherwise everything would need to be done twice (once for P2WPKH and once for P2TR).

> Are there still plans to support this? The main issue is not signing arbitrary scripts but how to describe the used scheme so Trezor can meaningfully show information about...