фото показано с : blog.trezor.io

Thanks to a report by Saleem Rashid via our responsible disclosure program, we were notified of a potential security vulnerability in Segwit transactions. This issue is a result of design choices in the Bitcoin protocol and is not a vulnerability specific to Trezor.

As this is a corner case, it is highly unlikely that you will encounter this problem. Segwit transactions are not affected if they are already on the blockchain and there is a rare possibility of this issue even if you are signing a new transaction while you have malware on your computer.

Even though this is a very improbable scenario and it will eventually be resolved by the Bitcoin community, SatoshiLabs is dedicated to correcting all problems, even those outside of normal operating parameters, no matter their likelihood. The firmware updates for Trezor One (version 1.9.1) and Trezor Model T (version 2.3.1) change how Segwit transactions are handled and correct this.

Unfortunately, some third-party tools like Electrum or PSBT-based tools like BTCPay Server and Wasabi Wallet do not allow Trezor to obtain the previous transaction in case of Segwit inputs, which is why Trezor will not be able to sign transactions using these tools until they are updated to work correctly. We are cooperating with these parties to fix the problem as we speak.

With every new firmware release, Trezor Wallet notifies you and will walk you through the process. Step by step instructions are also available in the user manual.

For more detailed information about these firmware updates, please refer to the technical update in our dev corner.

Latest Firmware Updates Correct Possible Segwit Transaction Vulnerability was originally published in Trezor Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.

149 +