Author: Jeremy 2021-07-08 20:06:08
Published on: 2021-07-08T20:06:08+00:00
The Bitcoin developer Jeremy Rubin has suggested that different keys should be allowed to specify different sighash flags, which would allow for greater flexibility in specifying signature requirements. For example, if a user wanted chaperone signatures with anyprevout, they would need to specify that the anyprevout key sign with APO and the chaperone sign with ALL. Similarly, Sapio emulator oracles currently sign with SIGHASH_ALL, but other signatories might be instructed to sign with a different flag. Currently, the sighashtype key is per-input, and if a sighash type is not provided, the signer should sign using SIGHASH_ALL, but may use any sighash type they wish. By allowing for a new per-key mapping, this could be changed to allow for more specific and granular signature requirements. There is no set format for this yet, but Rubin requested it when spec'ing V2 and hopes to get it implemented soon.
Updated on: 2023-06-14T23:25:44.910122+00:00