Secure Transaction Signing: Integrating Trezor into a Web Application
A client lost 2 BTC due to a hot wallet phishing attack. After that, they decided to move all funds to cold storage. We helped integrate Trezor into their DeFi platform so that transaction signing happened without key compromise. The client saved an average of $500 per month in transaction costs after integration. Below is how we did it and why Trezor requires a special approach. If you need a reliable integration, request an audit and turnkey deployment.
How Trezor Protects Against Attacks
Trezor is the second most popular hardware wallet after Ledger, with a fundamentally different communication architecture. While Ledger uses native WebHID/WebUSB, Trezor works through its own bridge: Trezor Suite Bridge or WebUSB transport. This affects how the integration is built and which scenarios to handle.
The Trezor Connect SDK (@trezor/connect-web) operates through an iframe hosted on connect.trezor.io. This means your code does not communicate with the device directly—the request goes to the iframe, which communicates with Trezor Suite Bridge (native app) or via WebUSB, receives the response, and returns it via postMessage.
This approach provides security (keys never leave the Trezor-controlled domain) and convenience (no additional software needed with WebUSB), but it creates a dependency on Trezor's infrastructure. According to the official documentation for @trezor/connect-web, the manifest is mandatory for identifying the application.
Why Trezor Integration Is Trickier Than Ledger
| Aspect | Ledger | Trezor |
|---|---|---|
| Transport | WebHID/WebUSB directly | iframe + Bridge/WebUSB |
| Infrastructure dependency | None | connect.trezor.io |
| Transaction format | RLP-encoded | Object with fields |
| Offline use | Yes | Limited |
| EIP-712 on budget models | Limited | metamask_v4_compat |
In our tests, the Model T processes EIP-712 signing 3x faster than the Model One thanks to hardware-accelerated cryptography.
Basic Integration
Initialization:
import TrezorConnect from "@trezor/connect-web"; await TrezorConnect.init({ lazyLoad: true, manifest: { email: "[email protected]", appUrl: "https://yourproject.com", }, }); The manifest is mandatory—Trezor uses it to identify the application and display it to the user on the device screen.
Getting an address:
const result = await TrezorConnect.ethereumGetAddress({ path: "m/44'/60'/0'/0/0", showOnTrezor: true, }); if (result.success) { console.log(result.payload.address); } else { console.error(result.payload.error); } Signing a transaction via TrezorConnect.ethereumSignTransaction. Unlike Ledger, Trezor expects an object with fields, not RLP:
const result = await TrezorConnect.ethereumSignTransaction({ path: "m/44'/60'/0'/0/0", transaction: { to: "0xRecipient", value: "0xDE0B6B3A7640000", // 1 ETH in hex data: "0x", chainId: 1, nonce: "0x5", gasLimit: "0x5208", maxFeePerGas: "0x...", // EIP-1559 maxPriorityFeePerGas: "0x...", }, }); EIP-712 Signing
Trezor supports ethereumSignTypedData starting from firmware 2.4.3 (Model T) and 1.10.5 (Model One). An important nuance: the Model One has a limited screen and cannot display complex structures—for this, it uses the metamask_v4_compat: true mode with host-side hashing.
const result = await TrezorConnect.ethereumSignTypedData({ path: "m/44'/60'/0'/0/0", data: typedData, // standard EIP-712 object metamask_v4_compat: true, }); Typical Problems
Bridge not running. If the user hasn't installed Trezor Suite Bridge and their browser doesn't support WebUSB, the SDK won't find the device. Solution: in the UI, direct them to the install page; detect transport availability via TrezorConnect.getFeatures().
Popup blocked. @trezor/connect-web opens a popup for permission requests. Browser popup blockers can prevent this. All calls must be initiated from a user gesture (click).
Firmware version. Older firmware does not support EIP-1559 transactions. We recommend checking the version via TrezorConnect.getFeatures() and showing an update warning.
Additional scenarios
For offline testing, you can use the Trezor simulator. It emulates the device via WebUSB and allows you to debug signing without a physical wallet.
Trezor Model Comparison
| Feature | Trezor Model One | Trezor Model T |
|---|---|---|
| Display | OLED 128×64 | Color touchscreen |
| EIP-1559 support | Yes (firmware 1.10.5+) | Yes |
| EIP-712 structure display | Limited (metamask_v4_compat) | Full |
| Price | Budget | Premium |
Our Process
- Requirements analysis and SDK selection (@trezor/connect-web or @trezor/connect)
- Manifest initialization and transport setup
- Address and signing implementation (ETH, ERC-20, EIP-712)
- Testing on both models with multiple firmware versions
- Deployment with monitoring and documentation
What's Included
- Integration documentation (API, configs)
- Test environment setup (Testnet)
- Transaction signing code with error handling
- Team training (2 hours online)
- 30-day post-release support
Our Experience and Guarantees
We have integrated Trezor into 15+ projects, from simple crypto wallets to complex DeFi platforms. We guarantee secure signing without key leaks. Our experience with hardware wallets spans 5 years and 30+ successful Web3 projects. Get a consultation on Trezor integration today—contact us to discuss the details.