Skip to content

Conversation

@jl2012
Copy link
Contributor

@jl2012 jl2012 commented Jul 27, 2016

CHECK(MULTI)SIG should be used.

@luke-jr
Copy link
Member

luke-jr commented Jul 27, 2016

@btcdrak @maaku @CodeShark

@luke-jr
Copy link
Member

luke-jr commented Jul 27, 2016

Personally, I think it's preferable to use the VERIFY...

@jl2012
Copy link
Contributor Author

jl2012 commented Jul 27, 2016

@luke-jr , technically you could do that, which requires an extra push in scriptSig

@luke-jr
Copy link
Member

luke-jr commented Jul 27, 2016

Why would it need an extra push? AFAIK, OP_CHECK[MULTI]SIGVERIFY behaves exactly as OP_CHECK[MULTI]SIG except that the VERIFY variant short-circuits script execution immediately.

@jl2012
Copy link
Contributor Author

jl2012 commented Jul 27, 2016

Without an extra push the stack will be empty after evaluation, which is invalid

@petertodd
Copy link
Contributor

petertodd commented Aug 18, 2016

@luke-jr The easiest way to convince us would be to make such a transaction on mainnet and show that it works. :)

edit: ah! now I see that @luke-jr was the thumbs-up emoji thing!

@petertodd
Copy link
Contributor

utACK

Though I'd suggest jl2012 take my advice. :)

@btcdrak
Copy link
Contributor

btcdrak commented Aug 18, 2016

ACK

@luke-jr luke-jr merged commit 2fceaf9 into bitcoin:master Sep 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants