Also the doccomment for this field should be changed. It currently says:
true if satisfactions cannot be created by any 3rd party who has not yet seen a satisfaction.
Hash preimages and signature checks are safe; timelocks are not. Affects malleability.
This is inaccurate. Hash preimages are not "safe" (which is why we renamed this term to "signed").
The code is correct, just the doccomment is wrong.
Also the doccomment for this field should be changed. It currently says:
This is inaccurate. Hash preimages are not "safe" (which is why we renamed this term to "signed").
The code is correct, just the doccomment is wrong.