Trezor updates
Trezor Model One firmware and Trezor Suite updates May 2021
Update your device and Suite by opening Trezor Suite and following the on-screen prompts
A new firmware update has been released for the Trezor Model One. No firmware update will be released for the Trezor Model T this month. To download and install the new Trezor Model One firmware simply open the Trezor Suite desktop app and follow on-screen instructions or visit the Trezor Wallet interface with your Trezor device connected, and click on the firmware update prompt which appears at the top.
In addition, the latest version of Trezor Suite is available to download. You will be prompted to update the next time you launch Trezor Suite. Alternatively, you can manually download and install the latest version from the Trezor Suite landing page.
Development is heating up as we look forward to some big announcements, so this month’s firmware and Suite releases contribute to a more robust Trezor ecosystem. Below, you will find a walkthrough of improvements and what they mean for Trezor devices and the overall user experience.
Trezor Suite update (version 21.5.1)
As the Trezor Suite public beta enters its eighth month, we are continuing to improve the user experience and implement new features that make using cryptocurrency easier and more secure.
Sell Bitcoin, if you must
We are pleased to announce that Invity, which celebrated its one-year anniversary last week, has now integrated all their Trade features into Trezor Suite. In addition to buy, spend and exchange, Trezor’s European customers can now sell cryptocurrency directly from Trezor Suite, through Invity’s partner BTC Direct.
To begin with, it is only possible to exchange Bitcoin for Euros, but Invity is working with partner exchanges to soon provide everyone with a fiat off-ramp and more cryptocurrency options, for when they really need to cash out some of their savings.
Safety checks
Safety checks, which help protect users from overpaying fees or signing transactions with the wrong derivation paths, can now be disabled directly through Suite, should users need to perform more advanced functions such as overriding derivation paths in cases where coins have been sent to the wrong address type.
Note that these safety checks protect from user error or a compromised device, so turning them off is only recommended for advanced users who know precisely what they are doing.
Secure remote messaging system
In case of emergency, it is now possible for secure, encrypted messages to be sent to Trezor Suite to alert users to any major issues that require attention.
Trezor Suite will only ever display a message signed by SatoshiLabs’ senior management, and the system will be reserved for communicating incidents such as upcoming hard forks, coin splits, vulnerabilities, and so on. Though there are no such events anticipated, this messaging system has been implemented so users can be sure the information they receive is legitimate.
Note that this system does not in any way provide access to Trezor devices and can not share information about Trezor Suite usage. Rather, it is a secure channel which will help communicate security concerns directly with users while mitigating any risk of phishing or spread of misinformation.
Bug fixes
A number of bug fixes have been corrected, including one issue where tor .onion links would not open correctly, a discrepancy between ETH and ERC-20 fee bumps, and one where a SegWit address was incorrectly converted to lowercase.
Each of these bugs occurred in a very small number of cases but we are always grateful for our users reporting them. Visit our May release GitHub project for a full breakdown of issues and features, including bug fixes.
If you encounter an issue in Suite, please report it using the Feedback button in Suite, which you can find by clicking on the Beta button in the bottom-right corner, or visit our feedback form directly.
Trezor Model One firmware update (version 1.10.0)
This month’s Trezor Model One hardware wallet firmware update will bring some behind-the-scenes improvements and a change to Locktime confirmation. Review the full changelog on GitHub.
Locktime
Locktime is a feature that helps preserve privacy by broadcasting a transaction only once a certain block height has been reached.
This means transactions can be delayed and broadcast from a different device or network. To do so, enter a future block height or Unix timestamp at which the transaction should broadcast after and sign the transaction. Then, save the raw hexadecimal data and broadcast it using a tool such as Trezor’s send raw transaction tool.
To make Locktime easier to use, Trezor Model One hardware wallets will now display the selected block height or timestamp in human-readable form when signing it on a device.
How to set a Locktime in Trezor Suite
If the Locktime is specified as a number below 500,000,000 it is interpreted as block height. The current block height can be viewed on any block explorer.
A Locktime of 500,000,000 or more is interpreted as a Unix timestamp and shown in UTC. For now, simply calculate the desired time and date using a Unix time calculator.
