You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the screen where transaction details are finalized (e.g., RBF, LockTime, Version; before signing), it would be a fantastic addition to include a preview of each input's hash-preimage that will be signed.
For users like me who are interested in the technical aspects of Bitcoin, this feature would provide valuable insight and enhance the debugging capabilities of the wallet (also educational ones). It could also serve as a great tool for verifying the exact data being signed, adding another layer of transparency for advanced users.
The text was updated successfully, but these errors were encountered:
When the transaction it's going to be signed, there are different preimages for each input.
For example, in a 2 input transaction with the SigHash flag ´ALL´, the preimage for the first input would set the ScriptPubKey of the second input to 0x00 and vice versa.
Right now, the "preimage" that Sparrow shows before signing is not the real preimage that it is going to be signed by each input's private key. So, in order to improve the debugging capabilities, it would be helpful to show the exact data that it is going to be signed for every input.
For instance, the following 3input-2output (SigHash SINGLE) tx:
Before signing Sparrow shows the following "preimage":
In the screen where transaction details are finalized (e.g., RBF, LockTime, Version; before signing), it would be a fantastic addition to include a preview of each input's hash-preimage that will be signed.
For users like me who are interested in the technical aspects of Bitcoin, this feature would provide valuable insight and enhance the debugging capabilities of the wallet (also educational ones). It could also serve as a great tool for verifying the exact data being signed, adding another layer of transparency for advanced users.
The text was updated successfully, but these errors were encountered: