Bitcoin full node and query server
Apr 5, 2018
View in context in the libbitcoin Slack #general mirror.
evoskuil06:55
NP, actually strike all of this: "sequence in the block version field, with each of the first 29 bits each representing support for a given BIP." (not in block version field, not 29 bits, not limited to BIPs).
4 replies · James C., evoskuil · last Apr 05, 2018
James C.11:26
This was a mental error of mine. I somehow thought Libbitcoin used the same bits in the rule_fork enum as used in the signalling during BIP activation. I now realise this is not true, bip112/113 used bit 0 for signalling, but occupy bits 9 and 10 in Libbitcoin, for example.
James C.11:28
Just wondering: In the rule_fork object, is the bit assignment per rule in the exact order of historic network majority adoption (save for test/regnet)?
(edited)evoskuil11:45
The order is unimportant though apart from the first two may reflect historical adoption.
👍 1