input-output-hk / input-output-hk/daedalus
Daedalus 11.3.0 cannot communicate with Trezor Model T on Windows
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 297
- Avg merge
- 10d 14h
- Merged PRs (30d)
- 10
Description
## Summary
After updating to Daedalus 11.3.0, a previously paired Trezor Model T can no longer confirm or sign transactions. Attempting to pair the device again remains stuck indefinitely.
The same device connects immediately through Trezor Suite on the same computer.
## Environment
Daedalus: 11.3.0
Build: adf90b52e
Cardano wallet: 2026.8.21-49e067900
Cardano node: 11.0.1-97036a66b
Network: Mainnet
Operating system: Windows 11, version 10.0.26200
Device: Trezor Model T
Trezor firmware: 2.11.1
## Steps to reproduce
1. Connect and unlock the Trezor Model T.
2. Open the previously paired hardware wallet in Daedalus.
3. Attempt to create and confirm a governance delegation transaction.
4. Daedalus reports “Transaction confirmation failed.”
5. Open the Add hardware wallet screen and attempt to pair the device.
6. Daedalus remains on the loading spinner indefinitely and never detects the Trezor.
## Expected behavior
Daedalus should connect to the Trezor and allow the user to confirm and sign the transaction. The device should also be detected when pairing a hardware wallet.
## Actual behavior
Transaction confirmation fails and the hardware wallet pairing process remains stuck indefinitely.
## Diagnostic evidence
The diagnostics show Daedalus repeatedly failing to establish the Trezor USB transport:
```text
[TREZOR-CONNECT] Received TRANSPORT_EVENT: transport-error
apiType: usb
error: Network request failed
```
The corresponding hardware wallet state reports:
```text
[HW-DEBUG] HWStore - CHANGE status:
deviceType: trezor
apiType: usb
error: Network request failed
```
These errors occur approximately once per second. The supplied diagnostics contain 309 consecutive transport failures between `2026-09-10T16:00:51.910Z` and `2026-09-10T16:06:02.279Z`.
During this period Daedalus was fully synchronized. The node and wallet backend were responsive and the wallet backend restart count was zero.
The complete diagnostic bundle is available through the associated support ticket and can be provided privately if needed.
## Additional context
The customer restarted Windows and opened Daedalus before testing again. The failure affects both transaction signing and new hardware wallet pairing.
The Trezor connects successfully through Trezor Suite on the same computer and its firmware is current. The customer reports that the device worked with Daedalus before the 11.3.0 update.
This appeared during the same release as the Ledger hardware wallet failures reported in #3400. The symptoms may share a release level cause but this report concerns the separate Trezor USB transport path.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.