craigraw
commented
1 week ago Sparrow already provides deep introspection on a transaction, making signature examination trivial. Adding another feature always risks software bloat, and I'm not sure this (no doubt rarely used) feature would be worth this cost.
Do you think that sparrow could add an option where you can sign the same transaction with a different HWW after already signing it with one and Sparrow just does the simple operation of checking if the Txn hex is the same on with fully signed Txns.
This would allow you to ensure that for the current software version on your wallets you should be fine with regards to a chosen nonce attack. I'm sure that it wouldn't be too hard to implement if you deem it to be a suitable feature.