Discourage unsigned / uncommitted annexes #10
+18
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been thinking about the possibility of witness malleability if the annex becomes standard. As it stands, any script path spend that lacks a CHECKSIG can have an arbitrary amount of data placed in the annex by a third party.
A simple solution would be to make unsigned annexes non-standard. I implemented this by adding a
m_annex_committed
field toScriptExecutionData
, which is only set totrue
ifCheckSchnorrSignature
executes successfully and an annex is present. I called this variablem_annex_committed
rather thanm_annex_signed
in case there is a future opcode that commits to the annex explicitly.@petertodd Do you think this is a good idea, if the annex is made standard? I'm not sure how common non-CHECKSIG scripts are today, but I imagine they could become more common if opcodes like CTV or CSFS are adopted in the future.