I understand the BIP9 version bits base is 0x20000000 because the BIP specifies that the first three bits must be 001

Bitcoin Classic adds one more "on" bit 0011... to make 0x30000000

Why did BitcoinXT add THREE bits to the end to make 0x20000007 instead of just flagging-on one single bit like classic? Or simply use 0x20000001?

  • A correction is needed to the question. BIP9 specifies the first three bits are 001, so the hex version will be at least 0x20000000. BIP109 uses the fourth bit to signal support, so the first four bits are 0011 with the rest zero, so the version is ``0x30000000`. – Tom Harding Apr 14 '16 at 16:46
  • @TomHarding thanks for catching that, edited – pinhead Apr 14 '16 at 16:49

Bitcoin XT versions 0.11A through 0.11D supported the withdrawn BIP101, which set version = 0x20000007 as a best-guess nod toward the developing versionbits standard, while trying to maximize backward compatibility with the ways nodes might check for compatible versions.

Bitcoin XT version 0.11E supports BIP109, identical to Bitcoin Classic.

  • "best-guess nod toward the developing versionbits standard" -- that's what I'm curious about. What were they thinking? – pinhead Apr 14 '16 at 16:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.