
Ledger and the Metadata Your Hardware Wallet Sends After You Sign - Uneasy Money
In this episode of Uneasy Money, the hosts discuss a controversial topic: the metadata that Ledger sends to its servers after signing a transaction.
The Problem: Post-Signing Telemetry
- Ledger's signing SDK sends metadata (addresses, transaction data) to Ledger's servers every time you sign a transaction.
- This happens after the signing process – without any necessity for the process itself.
- The V2 API removes some data but still allows address-to-user correlation.
The CTO's Contradiction
- The Ledger CTO claims this data is needed for Clear Signing (ensuring users only sign what they intend).
- The hosts debunk this as factually false or misleading because the metadata is sent after signing – not before.
- Quote: "Why the hell do you sign the transaction first and then send the metadata?"
Clear Signing: An Unsolved Problem
- Clear Signing is a standard (~§330 or §7730? 7730) that shows users exactly what they are signing.
- Ledger argues their devices have too little memory for Clear Signing.
- Critics: "They could have just added more memory – 256 GB is possible!"
- Instead, they offload the analysis to external servers, creating a security risk.
Security Concerns
- Telemetry is sent even for failed transactions – an unnecessary attack surface.
- Example: Bybit was compromised due to an attack on the pre-transaction API.
- Conclusion: "You can't just start blasting telemetry data."
Bottom Line: Hardware Wallets Not for End Users
- The hosts view hardware wallets as YubiKey equivalents – just an interface to a secure device.
- Irony: "We're just using them wrong."
- Recommendation: Clear Signing and dynamic data (e.g., ENS or proxy contracts) need a trusted server to sign the information.






