Add a BIP to define 24 bits of nVersion as nonce space not 16#2116
Open
TheBlueMatt wants to merge 1 commit intobitcoin:masterfrom
Open
Add a BIP to define 24 bits of nVersion as nonce space not 16#2116TheBlueMatt wants to merge 1 commit intobitcoin:masterfrom
TheBlueMatt wants to merge 1 commit intobitcoin:masterfrom
Conversation
murchandamus
reviewed
Mar 5, 2026
| <pre> | ||
| BIP: ? | ||
| Title: 24 nVersion bits for general purpose use | ||
| Author: Matt Corallo <bips@bluematt.me> |
Member
There was a problem hiding this comment.
Suggested change
| Author: Matt Corallo <bips@bluematt.me> | |
| Authors: Matt Corallo <bips@bluematt.me> |
| Author: Matt Corallo <bips@bluematt.me> | ||
| Status: Draft | ||
| Type: Specification | ||
| Created: 2026-02-26 |
Member
There was a problem hiding this comment.
Suggested change
| Created: 2026-02-26 | |
| Assigned: ? |
|
|
||
| ==Rationale== | ||
|
|
||
| Headers-only mining avoids mining devices (either ASICs or the firmware) from having to concern itself with the vast space of consensus logic (handling transactions, merkle trees, etc). It is widely deployed in ASICs, but requires a substantial number of jobs fed across an entire device, keeping the ASIC controller busy. Providing additional nonce space for the ASICs to roll without needing fresh work from the controller may simplify ASIC design somewhat, and as been apparently adopted in some miners by using extra space in nTime as extra nonce space. Doing so in nVersion instead is preferable to using nTime. |
Member
There was a problem hiding this comment.
Suggested change
| Headers-only mining avoids mining devices (either ASICs or the firmware) from having to concern itself with the vast space of consensus logic (handling transactions, merkle trees, etc). It is widely deployed in ASICs, but requires a substantial number of jobs fed across an entire device, keeping the ASIC controller busy. Providing additional nonce space for the ASICs to roll without needing fresh work from the controller may simplify ASIC design somewhat, and as been apparently adopted in some miners by using extra space in nTime as extra nonce space. Doing so in nVersion instead is preferable to using nTime. | |
| Headers-only mining avoids mining devices (either ASICs or the firmware) from having to concern themselves with the vast space of consensus logic (handling transactions, merkle trees, etc). It is widely deployed in ASICs, but requires a substantial number of jobs fed across an entire device, keeping the ASIC controller busy. Providing additional nonce space for the ASICs to roll without needing fresh work from the controller may simplify ASIC design somewhat, and has been apparently adopted in some miners by using extra space in nTime as extra nonce space. Doing so in nVersion instead is preferable to using nTime. |
Also, for legibility of review comments, it would be preferable if you limited the length of the lines in the document.
Comment on lines
+8
to
+9
| License: BSD-3-Clause | ||
| CC0-1.0 |
Member
There was a problem hiding this comment.
Since BIP3 deployed, we are using License Expressions for the License header values: https://github.com/bitcoin/bips/blob/master/bip-0003.md#specification-1
Suggested change
| License: BSD-3-Clause | |
| CC0-1.0 | |
| License: BSD-3-Clause OR CC0-1.0 |
|
|
||
| Timo Hanke and Sergio Lerner for originally proposing 15-bit extra nNonce2. Btc Drak for writing BIP 320. | ||
|
|
||
| ==Changelog== |
Member
There was a problem hiding this comment.
Nit: It would be preferable to only add this section when it has content.
| Created: 2026-02-26 | ||
| License: BSD-3-Clause | ||
| CC0-1.0 | ||
| Replaces: 320 |
Member
There was a problem hiding this comment.
I saw that this was discussed on the mailing list. Please add a Discussion header:
Suggested change
| Replaces: 320 | |
| Discussion: 2026-02-26: https://gnusha.org/pi/bitcoindev/6fa0cb45-37d6-4b41-9ff8-03730fd96d6e@mattcorallo.com/ | |
| Replaces: 320 |
Please also add the corresponding Proposed-Replacement header to BIP 320.
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
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.
No description provided.