Skip to content

Conversation

@dcousens
Copy link
Contributor

Thanks to @bpdavenport for the initial implementation of this, however there was some issues with the existing implementation in f7604b8 that meant all multisig signatures were considered complete even though they weren't.

To allow for this without breaking backwards compatibility, I have added the allowIncomplete flag and appropriate tests.

@bpdavenport does this look good to you?

This should bode well with the txbmerge changes and ideally be merged in the next 24 hours.

@dcousens dcousens force-pushed the wipscript branch 2 times, most recently from 461610e to f221545 Compare February 11, 2015 03:11
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

null is re-interpreted as OP_0 as seen on line 148.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this type is used when the allowIncomplete flag is true

@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 98.26% when pulling c35d4b4 on wipscript into 7ad3ac5 on master.

dcousens added a commit that referenced this pull request Feb 13, 2015
scripts: add allowIncomplete for multisig scripts
@dcousens dcousens merged commit 18fb33d into master Feb 13, 2015
@dcousens dcousens deleted the wipscript branch February 13, 2015 00:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants