Author: Jeremy 2021-07-06 17:54:57
Published on: 2021-07-06T17:54:57+00:00
The conversation revolves around the implementation of the `OP_CHECKSIGFROMSTACK` opcode and the different options available to split R and s values or variable-length messages. The four options discussed are making a new 64 byte PK standard, splitting (R,S), using different opcodes, and CAT. Each option has its own drawbacks, such as being designed for specific use cases, requiring an extra push byte for every use, or wasting opcodes. To determine the usefulness of splitting R/S, interesting script fragments that people are aware of are listed. These include using a specific R Value, reusing arbitrary R for a specific M (pay to leak key), verifying two different messages reuse the same R, and using an R Value signed by an oracle.
Updated on: 2023-06-14T23:59:14.483512+00:00