You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how this escaped previous testing, but it appears the e731395 in v2.2.0 has broken signing of multisig transactions on both Trezor One and Trezor T for Segwit script types on standard derivation paths. Signatures are returned, but are invalid and fail verification. The results of my testing as follows:
Script Type
Derivation Path
v2.1.1
v2.2.0
P2WSH
m/48'/1'/0'/2'
Yes
Fails verification
P2SH-P2WSH
m/48'/1'/0'/1'
Yes
Fails verification
P2SH
m/45'
Yes
Yes
P2SH
m/45'/0/0/0
Error: Multisig field provided but not expected
Yes
Testing also reveals the change in e731395 is the sole reason for the difference between the two versions.
Firmware versions 2.5.3 & 1.11.0, bitcoin only.
The text was updated successfully, but these errors were encountered:
I'm not sure how this escaped previous testing, but it appears the e731395 in v2.2.0 has broken signing of multisig transactions on both Trezor One and Trezor T for Segwit script types on standard derivation paths. Signatures are returned, but are invalid and fail verification. The results of my testing as follows:
Testing also reveals the change in e731395 is the sole reason for the difference between the two versions.
Firmware versions 2.5.3 & 1.11.0, bitcoin only.
The text was updated successfully, but these errors were encountered: