Trezor has switched on a long-awaited layer of transaction security, rolling out Trezor ERC-7730 signing across its Safe hardware wallet lineup and the Model T device. The move, confirmed jointly by Trezor and the Ethereum Foundation on September 8, replaces the wall of unreadable hexadecimal data that hardware wallet owners have stared at for years with something far more useful: a plain-language description of what a transaction actually does before you approve it.
Key takeaways
- Trezor has enabled the ERC-7730 standard for clear signing on its Safe wallets and the Model T, confirmed alongside the Ethereum Foundation.
- ERC-7730 decodes smart contract calls into readable actions, token amounts, and destination addresses instead of raw calldata hashes.
- Blind signing has been tied to some of crypto’s costliest thefts, including the $1.5 billion Bybit hack.
- The feature works automatically through Trezor Suite, WalletConnect, and Trezor Connect, with no manual setup required.
- Launch support covers 1inch, Aave, Lido, Tether, LiFi, and Hyperliquid, with the Trezor Safe 7, Safe 5, Safe 3, and Model T compatible — the Model One is not.
Trezor activates ERC-7730 clear signing on Safe wallets
Trezor’s adoption of ERC-7730 means its hardware wallets can now decode smart contract transactions and show users exactly what they’re signing, rather than an unreadable string of code. The announcement, made jointly with the Ethereum Foundation, extends a security initiative the Foundation first set in motion in May to a new set of hardware devices.
What ERC-7730 standard means for hardware wallets
Before this update, a Trezor user asking to “swap 2,000 USDC for ETH” would see that description on their computer screen, but the data actually reaching the hardware device arrived as a hash of hexadecimal calldata nobody could realistically read. Approving that transaction meant trusting that the computer’s description matched what was really being signed. If the machine had been compromised, there was no way to catch the mismatch on the device itself. ERC-7730 closes that gap by letting the wallet pull the transaction apart and render it in plain terms: the action being performed, the tokens and amounts involved, and where the funds are heading.
Supported Trezor devices and protocols at launch
On the hardware side, clear transaction signing runs on the Trezor Safe 7, Safe 5, Safe 3, and Model T. The original Trezor Model One does not support the feature, and devices need updated firmware to take advantage of it. Protocol coverage at launch includes 1inch, Aave, Lido, Tether, LiFi, and Hyperliquid — a mix of DeFi and stablecoin infrastructure that represents a meaningful chunk of everyday on-chain activity. More networks are reportedly in progress, and the underlying registry of supported contracts has expanded quickly, growing by roughly 28% in its first few months of existence, according to reporting from Crypto Briefing.
Mitigating blind signing to prevent crypto thefts
Blind signing — approving a transaction without being able to verify what it actually contains — has been linked to some of the most expensive crypto heists on record, including the $1.5 billion Bybit breach, still the largest crypto hack ever documented. That history is exactly why the Ethereum Foundation has been pushing standards like ERC-7730 across the wallet ecosystem.
Blind signing risks and real-world theft examples
The core problem with blind signing is that it hands total trust to the computer or dApp interface a wallet is connected to. A phishing site or compromised browser extension can display one transaction on screen while quietly submitting a completely different one to the hardware device. Without a way to read the raw calldata, the wallet owner has no independent check — they either trust the screen or they don’t sign at all. That blind spot has been exploited repeatedly across the industry, turning token approvals, contract calls, and wallet-connect sessions into common attack surfaces.
How clear signing enhances transaction verification
This is why the shift matters: with Trezor ERC-7730 signing active, the hardware device itself becomes the final source of truth, not the potentially compromised computer it’s plugged into. Trezor says users don’t need to install anything or flip a switch — the protection works automatically through Trezor Suite, WalletConnect, and Trezor Connect, and the normal signing workflow stays the same. That “no extra steps” design matters for adoption, since security features that require manual setup tend to get skipped by everyday users.
Governance and technical framework behind ERC-7730
ERC-7730 isn’t a Trezor invention — it’s an open, shared standard that any wallet maker can build on, which is part of why its rollout carries weight beyond a single brand. Ledger originally developed the underlying idea internally before formalizing it as ERC-7730 in 2024, then handed governance over to the Ethereum Foundation to keep the standard neutral and vendor-agnostic. Trezor’s own decoding stack is open-source as well, built to work with its existing firmware.
Open-source standard development and Ethereum Foundation stewardship
Handing the standard to the Ethereum Foundation rather than keeping it under one company’s control is a deliberate choice. It signals that ERC-7730 is meant to function as shared infrastructure across competing hardware wallet brands, similar to how open web standards avoid being tied to a single browser maker. Trezor and Ledger collaborating on the same underlying framework, rather than building rival proprietary systems, gives protocol developers one target to build for instead of several.
Role of the clearsigning.org registry and smart contract descriptors
For clear signing to work on any given transaction, the smart contract involved needs a descriptor listed in the clearsigning.org registry. These descriptors sit off-chain and act like a translation layer, letting existing contracts adopt readable signing without needing to be redeployed. An attestation layer also allows independent auditors to confirm that a descriptor accurately reflects what a contract really does. The Ethereum Foundation’s Trillion Dollar Security Initiative — this initiative powers the One Trillion Dollar Security Dashboard that was unveiled in February — stewards that registry going forward.
The catch is that protection only extends as far as the registry does. Contracts without a published descriptor still trigger the old blind-signing warning, meaning users interacting with newer or smaller protocols may not get the same clarity as those using 1inch, Aave, or Lido. In that sense, the security payoff of hardware wallet security upgrades like this one scales directly with how many developers bother to publish descriptors — the standard helps exactly where a dApp has done the work, and not a step further.
FAQ
What is the ERC-7730 standard?
ERC-7730 is an open standard that lets wallets decode smart contract transactions to show readable actions, tokens, amounts, and destinations on device screens.
Which Trezor devices support ERC-7730 clear signing?
Trezor Safe 7, Safe 5, Safe 3, and Model T support the feature; the Model One does not.
Does clear signing work for every smart contract transaction?
No, only smart contracts with descriptors registered in the ERC-7730 registry support clear signing; others revert to blind-signing warnings.
Does the user need to enable clear signing manually on Trezor devices?
No, the feature works automatically with Trezor Suite, WalletConnect, and Trezor Connect without user action.
Article produced with the assistance of artificial intelligence and reviewed by the editorial team.
Be the first to comment