/bitcoin.org

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

Already on GitHub? Sign in to your account

Number of fields for an input is wrong #1542

Closed
Huntrr opened this Issue Mar 13, 2017 · 2 comments

Comments

Assignees

@wbnns wbnns

Labels
Dev Docs
Projects
None yet
Milestone
No milestone
3 participants
@Huntrr @laanwj @wbnns
@Huntrr

Huntrr commented Mar 13, 2017

Location: https://bitcoin.org/en/glossary/input

Inputs are defined as having four fields but only three fields are listed. I believe this sentence

An input in a transaction which contains four fields: an outpoint, a signature script, and a sequence number

Should be

An input in a transaction contains three fields: an outpoint, a signature script, and a sequence number

Either that or the fields listed are wrong.

@wbnns wbnns added Dev Docs Under Review labels Mar 13, 2017

@wbnns wbnns self-assigned this Mar 13, 2017

@wbnns wbnns added Pull Request Welcome and removed Under Review labels Mar 13, 2017

@laanwj
Contributor

laanwj commented Mar 14, 2017

Huh. Maybe the writer was counting outpoint as two fields (hash,n). In any case it's worded wrongly.

wbnns added a commit that referenced this issue Mar 17, 2017

@wbnns
glossary: Fix typo in number of fields 
This Resolves an issue where the number of fields for an input was
incorrectly worded as four instead of three.

Resolves #1542
This commit was signed with a verified signature.
@wbnns wbnns Will Binns
GPG key ID: 302EBEAEEB74A404 Learn about signing commits

All checks have passed

2 successful checks
continuous-integration/travis-ci/pr — The Travis CI build passed
Details
continuous-integration/travis-ci/push — The Travis CI build passed
Details
862aea4

@wbnns wbnns referenced this issue Mar 17, 2017

Merged

glossary: Fix typo in number of fields #1545

@wbnns
Contributor

wbnns commented Mar 17, 2017

Thanks guys, I've submitted PR #1545 to resolve this. It will be live and fixed, shortly.

@wbnns wbnns closed this in #1545 Mar 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment