Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: Slight clarity boost to SEQUENCE_LOCKTIME_DISABLE_FLAG #15179

Closed
wants to merge 1 commit into from
Closed

doc: Slight clarity boost to SEQUENCE_LOCKTIME_DISABLE_FLAG #15179

wants to merge 1 commit into from

Conversation

instagibbs
Copy link
Member

The BIP is clear enough, but CTxIn::SEQUENCE_LOCKTIME_DISABLE_FLAG sounds like it's being acted upon the CTxIn field nSequence rather than the script operand.

@maflcko maflcko changed the title [trivial] Slight clarity boost to SEQUENCE_LOCKTIME_DISABLE_FLAG doc: Slight clarity boost to SEQUENCE_LOCKTIME_DISABLE_FLAG Jan 16, 2019
@jl2012
Copy link
Contributor

jl2012 commented Jan 20, 2019

Actually CTxIn::SEQUENCE_LOCKTIME_DISABLE_FLAG acts upon both CTxIn field nSequence and the script operand.

@instagibbs
Copy link
Member Author

Not sure how I missed this.

@instagibbs instagibbs closed this Jan 20, 2019
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
Consensus Docs
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@instagibbs @jl2012 @maflcko