Hi Trezor team,
I ran into a Bitcoin send bug in Trezor Suite Desktop 26.10.3 on Windows. I’m using Bitcoin mainnet with the default Trezor backend. The backend shows as connected.
Steps to reproduce
- Turn off MEV protection under Settings → App → Security.
- Create a BTC transaction and approve it on the Trezor device.
- Click Send in Trezor Suite after signing.
Actual behavior
Suite displays Transaction must be hexadecimal. The error persisted after reinstalling 26.10.3. Turning MEV protection back on allowed me to send BTC successfully using the same backend.
Expected behavior
BTC transactions should broadcast with either MEV protection setting.
Possible cause
The shared getMevProtectedTxData helper appears to wrap the signed BTC transaction in { hex, disableAlternativeRPC: true } when MEV protection is off. The Bitcoin pushTransaction method expects a hex string and rejects the object before broadcasting. I reproduced this parameter check offline with dummy hex data. Transaction formatting · Broadcast validation
Could you make the BTC send path pass the signed hex string regardless of the MEV protection setting?
Thanks!