Fixing SegWit spends being considered non-standard#1
Open
hsjoberg wants to merge 5 commits into
Open
Conversation
Segwit inputs in a transaction failed because ScriptSigArgsExpected(), which checks number of scriptSig arguments for an output, was missing checks for Segwit programs. This fix should make SegWit spends allowed in the mempool.
jc23424
force-pushed
the
segwit-claim
branch
2 times, most recently
from
4a74cb2 to
c2fd422
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This makes the client succeed sending a Segwit output using
sendrawtransaction.Nodes running this should also accept transactions spending segwit outputs.