If you use a hardware wallet for DeFi, the dangerous moment is not typing your PIN. It is approving a swap or token approval while your laptop shows "Swap 2,000 USDC for ETH" and your device only shows a hex hash. That blind-signing gap is how drainers win even when the seed never left the chip.
On 7 September 2026, Trezor turned on Clear Signing built on ERC-7730: for supported smart contracts, Safe 7, Safe 5, Safe 3, and Model T now decode the real action, tokens, amounts, and addresses on the trusted screen. No toggle and no extra app. Coverage still depends on the contract registry, so unsupported calls fall back to the old blind-signing warning.
This is the biggest Trezor security story since our July Suite 26.7 firmware recap, and it lands in the same week Ledger and Trezor jointly pushed for coordinated vulnerability disclosure across the industry.
What Clear Signing changes
Blind signing means you trust whatever your browser or dApp prints on the monitor. Malware or a compromised frontend can show a benign label while the calldata on-device is a wallet drain.
Clear Signing flips the trust model: the hardware screen becomes the source of truth. Trezor pulls supported contract metadata from the ERC-7730 registry, parses the call, and shows plain-language fields (action, asset, amount, destination) before you confirm.
Important limits:
- Registry-based — only contracts with a supported ERC-7730 descriptor get decoded. Everything else still blind-signs.
- EVM-focused — Ethereum mainnet, major L2s, and other EVM chains Trezor already supports.
- Automatic — works through Trezor Suite, WalletConnect, and Trezor Connect after firmware update. No setting to enable.
At launch Trezor listed major protocols including 1inch, Aave, Lido, Tether, LiFi, and Hyperliquid, with more registry entries in progress.
Why ERC-7730 matters beyond Trezor
Ledger pioneered human-readable transaction decoding internally, then open-sourced the idea as ERC-7730 in 2024. The Ethereum Foundation has been pushing adoption so wallets and dApps share one descriptor format instead of every vendor inventing its own parser.
Trezor's stack (firmware parsing + display pipeline) is open source, which matches the audit culture we called out in hardware wallet security with no compromise. Clear signing is not a marketing checkbox. It is the day-to-day control that stops "I thought I was swapping" mistakes.
Which Trezor models support it
| Model | Clear Signing (Sep 2026) |
|---|---|
| Trezor Safe 7 | Yes |
| Trezor Safe 5 | Yes |
| Trezor Safe 3 | Yes |
| Model T | Yes |
| Model One | No (EVM clear signing not available) |
If you are on Model One for Ethereum DeFi, you are still in blind-signing territory for contract calls. That is a real reason to consider Safe 3 or newer for anything beyond simple sends. Compare models in our Trezor Safe 7, Safe 5, and Safe 3 reviews, or the Ledger vs Trezor head-to-head.
Ledger devices have offered clear signing on many EVM flows for years via their own ERC-7730 implementation. If your threat model is heavy DeFi on multiple chains, read both ecosystems honestly. Our best DeFi hardware wallets roundup maps where each brand fits (no single device wins every chain).
Suite 26.9.2: the software half
Hardware decoding is only half the workflow. Trezor's September 2026 Suite 26.9.2 release adds companion protections:
- Blockaid transaction simulation extended beyond EVM to Solana, Tron, and Stellar
- Swap confirmations show a transaction simulation on the confirm page
- Solana root derivation path (
m/44'/501') to ease migrations from other wallets - Phishing-flagged transactions hidden from Activity Center notifications
Update Suite from trezor.io only, accept the firmware prompt on-device, and ignore email "update" links. Phishing spikes follow security news cycles, as we documented after the Coldcard migration wave.
Same week: disclosure norms and other patches
On 7 September, Ledger CTO Charles Guillemet published an open letter urging standardized coordinated disclosure, with Trezor security leadership publicly backing a 90-day fix-or-publish baseline. The subtext is practical: AI tooling shortens the window between a public patch and exploit scripts for users who delay updates.
You do not need to follow vendor politics to act:
- Trezor Safe owners — install Clear Signing firmware + Suite 26.9.x now if you touch DeFi.
- Ledger users — Ethereum app 1.22.2 (13 August) fixed a signing issue; keep Ledger Wallet current. See our Ledger Nano X review for the broader SE + app stack.
- BitBox02 users — firmware 9.26.5+ (17 August) patched two severe issues; 9.27.1 followed 31 August.
None of those stories replace Clear Signing, but they reinforce the same habit: patch promptly, then read what the device shows.
What Clear Signing does not fix
Be precise about the threat model:
- Unsupported contracts still blind-sign. Novel drainers on unaudited descriptors are not magically safe.
- Address poisoning and social engineering still work if you skip receive-address verification on-device.
- Seed generation bugs (the Coldcard lesson) are a different class from signing UX. Clear Signing does not retroactively fix weak entropy.
- Supply-chain tampering still starts with where you buy the device.
Clear Signing closes the gap between a pretty desktop UI and what you actually authorize. It does not remove the need for multisig, passphrase discipline, or a second vendor for large balances.
WalletLab take
September 2026 is a good month to treat your hardware wallet screen like a contract, not a formality. Trezor's ERC-7730 launch is the kind of firmware upgrade that quietly prevents losses: readable approvals on Safe 7/5/3 and Model T, with honest fallback warnings when metadata is missing.
If DeFi is why you own a hardware wallet, prioritize devices and firmware that make on-screen review unavoidable. Start with our Trezor reviews linked above, cross-check Ledger vs Trezor, and use /best-for/defi when you need a chain-specific shortlist.