Posted by Anthony Towns
Oct 1, 2019/14:45 UTC
In a Bitcoin development discussion, the idea of creating a new opcode called OP_CHECKSIG_WITHOUT_INPUT
was proposed as an alternative to SIGHASH_NOINPUT
. However, one participant in the discussion pointed out that there wouldn't be any meaningful difference between creating a new opcode and making a new tapscript public key type. The only difference would be in the encoding of the code. The proposed new opcode would ignore any SIGHASH
flags on a signature if present. It's worth noting that how sighash flags are treated can be redefined by new public key types.
Thread Summary (35 replies)
Sep 30 - Oct 5, 2019
36 messages • 35 replies
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback