Large multisig transaction causes firmware error when trying to sign

Suite issues Wallet issues
, ,
1

Signing a transaction with large data causes one of the steps in the preview for the transaction to throw a generic firmware error and revert the signature.

Reproducer (verified on two different wallets, running Universal 2.8.0 firmware, using Rabby desktop, both on Windows 10 and MacOS Sonoma):

https://app.safe.global/transactions/tx?safe=arb1:0xBbE98D590d7eB99F4a236587f2441826396053d3&id=multisig_0xBbE98D590d7eB99F4a236587f2441826396053d3_0x65a851e60545680bd7c3109792df867e1c1c2748f5e67e8c5e52fe458c9ccfa6

2

Just want to add a +1 on this. Large transactions fail for me using Trezor with Rabby. This was a large multisig transaction that I can no longer test against, but I believe I also tested this with Trezor and Metamask with the same results. Firmware error pops up on the Trezor.

1 Like
3

As Metanull also reported about this is still an issue. Another transaction came up (now about a year later) with large calldata. Firmware error thrown and unable to sign.