Hi @alexa , there has been an issue in a previous version of Trezor Suite which may have prevented this transaction from being signed correctly.
Could you please update to the latest version (26.3.1) and try completing the transaction again afterward? You may need to join the Early Access Program (EAP) to access this version
Would like to report that I am experiencing this exact same issue using Trezor Suite Web & Desktop on a Trezor Model T
I have elected to opt-in to the Early Access Program through Desktop Suite. I have tried using different wallet extensions (Metamask, Rabby, etc) and they all seem to fail on this same problem.
I have also attempted to connect to Remix using WalletConnect through the Suite; and get the same thing.
Trezor T - 2.11.1
Trezor Suite Desktop - 26.4.2
Why the Handshake is Failing:
The error Invalid parameter "to" (= undefined): Expected required property is a validation failure occurring in the Trezor Connect bridge (the software layer between your browser and your hardware).
The Mismatch: When you hit “Deploy” in Remix, it correctly generates a transaction with an empty to field. However, when this request passes through the WalletConnect or Trezor Bridge layer, the bridge’s internal schema incorrectly flags the empty field as “missing” rather than “valid for deployment.”
The Result: The bridge aborts the process and sends the “Invalid Parameter” error back to the UI before it ever reaches your Trezor device. This is why your Trezor never prompts you to sign; the software has already killed the request.