1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-04 11:08:05 +01:00

BIP 9: Clarify nVersion interpretation and bit order

This commit is contained in:
Luke Dashjr 2016-03-30 21:58:51 +00:00
parent ad9fc9ccea
commit b8907db950

View file

@ -51,6 +51,8 @@ With each block and soft fork, we associate a deployment state. The possible sta
===Bit flags=== ===Bit flags===
The nVersion block header field is to be interpreted as a 32-bit little-endian integer (as present), and bits are selected within this integer as values (1 << N) where N is the bit number.
Blocks in the STARTED state get an nVersion whose bit position bit is set to 1. The top 3 bits of such blocks must be Blocks in the STARTED state get an nVersion whose bit position bit is set to 1. The top 3 bits of such blocks must be
001, so the range of actually possible nVersion values is [0x20000000...0x3FFFFFFF], inclusive. 001, so the range of actually possible nVersion values is [0x20000000...0x3FFFFFFF], inclusive.