Trezor has enabled the ERC-7730 plaintext signature function on the Safe series of hardware wallets and the Model T. On September 8th, Trezor confirmed this update in conjunction with the Ethereum Foundation. The main change is that the hexadecimal data, which was previously difficult to identify on the devices, has been replaced with more readable transaction descriptions, making it easier for users to see the details of the transactions before confirmation.
Transactions can be directly verified on the device.
Before this update, users on the computer might see prompts such as "Exchange 2,000 USDC for ETH", but what actually gets transferred to the hardware wallet is often just the original calldata hash. Whether the user signs or not actually depends on whether the instructions provided by the computer or the dApp interface are accurate.
After enabling ERC-7730, hardware wallets can disassemble smart contract calls and directly display the specific actions, token types, quantities, and the whereabouts of funds on the device. In this way, users no longer have to rely solely on external interfaces to determine the content of transactions.
The first batch covers the Safe series and Model T.
The devices that currently support this feature include Trezor Safe 7, Safe 5, Safe 3, and Model T. The original Model One does not support it yet, and the device will need to have its firmware updated before it can be used.
- The first batch of supported devices includes Safe 7, Safe 5, and Safe 3.
- Model T is compatible, Model One is not supported yet.
- The feature can be enabled after a firmware update.
In terms of protocols, the first batch includes 1inch, Aave, Lido, Tether, LiFi, and Hyperliquid. Trezor indicates that this feature can be automatically activated through Trezor Suite, WalletConnect, and Trezor Connect; users do not need to enable it manually, and the existing signing process will not change.
The risk of blind signing remains a major pain point.
The so-called blind signature refers to the situation where users directly approve a signature without being able to verify the actual content of the transaction. This type of risk has long existed in the interactions between wallets and dApp, and it is also a common entry point for attacks by phishing websites, malicious browser plugins, and forged transaction pages.
The article mentions that the issue of blind signatures has been associated with several high-value crypto asset theft incidents, including the $1.5 billion attack on Bybit. The purpose of using plaintext signatures is to bring the final verification process back to the hardware device itself, rather than relying entirely on computer interfaces that may have been tampered with.
Unregistered contracts will still prompt for blind signing.
ERC-7730 is not an exclusive standard of Trezor. This standard was initially promoted and established by Ledger in 2024, and thereafter was handed over to the Ethereum Foundation for governance to maintain neutrality and universality. The parsing components of Trezor are also built using an open-source approach.
However, this protection does not cover all smart contracts. To implement plaintext signatures, the relevant contracts need to first register a descriptor at clearsigning.org. For contracts without a descriptor, the device will still display the traditional blind signature warning.
This means that when users are using protocols such as 1inch, Aave, or Lido which have already been integrated, they can obtain clearer signature prompts; however, when dealing with newer protocols or those with less coverage, the readability of transactions may still be insufficient. The actual effect of plaintext signatures still depends on how many protocol developers complete the release of descriptors.
