Bitcoin Forum
May 12, 2024, 10:41:07 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Bitcoin Forum > Bitcoin > Development & Technical Discussion > Why was the 6th ServiceFlags bit skipped?
Pages: [1]
« previous topic next topic »
  Print  
Author Topic: Why was the 6th ServiceFlags bit skipped?  (Read 85 times)
Coding Enthusiast (OP)
Legendary
*
Offline Offline

Activity: 1039
Merit: 2783


Bitcoin and C♯ Enthusiast


View Profile WWW
October 12, 2020, 03:41:25 PM
Merited by Welsh (3), ABCbits (1), Heisenberg_Hunter (1), darosior (1)
 #1
The ServiceFlags enum is jumping from the previously defined 5th bit (1 << 4 ie XThin) to 7th bit (1 << 6 ie CompactFilters). I couldn't find the 6th bit ever being set in the history of protocol.h file so is there any reason for this jump?

https://github.com/bitcoin/bitcoin/blob/af22322dab1a2277483b2512723491a5fad1a606/src/protocol.h#L268-L302
Projects List+Suggestion box
Donate: 1Q9s or bc1q
|
|
|
FinderOuter(0.19.1)Ann-git
Denovo(0.7.0)Ann-git
Bitcoin.Net(0.26.0)Ann-git
|
|
|
BitcoinTransactionTool(0.11.0)Ann-git
WatchOnlyBitcoinWallet(3.2.1)Ann-git
SharpPusher(0.12.0)Ann-git
1715553667
Hero Member
*
Offline Offline

Posts: 1715553667

View Profile Personal Message (Offline)

Ignore
1715553667
1715553667
Reply with quote  #2
1715553667
Report to moderator
1715553667
Hero Member
*
Offline Offline

Posts: 1715553667

View Profile Personal Message (Offline)

Ignore
1715553667
1715553667
Reply with quote  #2
1715553667
Report to moderator
1715553667
Hero Member
*
Offline Offline

Posts: 1715553667

View Profile Personal Message (Offline)

Ignore
1715553667
1715553667
Reply with quote  #2
1715553667
Report to moderator
"In a nutshell, the network works like a distributed timestamp server, stamping the first transaction to spend a coin. It takes advantage of the nature of information being easy to spread but hard to stifle." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715553667
Hero Member
*
Offline Offline

Posts: 1715553667

View Profile Personal Message (Offline)

Ignore
1715553667
1715553667
Reply with quote  #2
1715553667
Report to moderator
1715553667
Hero Member
*
Offline Offline

Posts: 1715553667

View Profile Personal Message (Offline)

Ignore
1715553667
1715553667
Reply with quote  #2
1715553667
Report to moderator
1715553667
Hero Member
*
Offline Offline

Posts: 1715553667

View Profile Personal Message (Offline)

Ignore
1715553667
1715553667
Reply with quote  #2
1715553667
Report to moderator
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 3388
Merit: 6635


Just writing some code


View Profile WWW
October 12, 2020, 03:51:54 PM
Merited by Welsh (6), ABCbits (2), Coding Enthusiast (2), Heisenberg_Hunter (1), darosior (1)
 #2
It's because both Bcash and Segwit2x occupied some service bits to indicate their own forks while they were still able to connect to Bitcoin nodes.

Bcash was using bit 6, and Segwit2x was using bit 8. Both bits thus needed to be skipped for some time to avoid collisions. See https://github.com/bitcoin/bitcoin/pull/10982
Bitcoin Core contributor | Tip Me! | GitHub | GPG Key Fingerprint 0x17565732E08E5E41
Pages: [1]
  Print  
Bitcoin Forum > Bitcoin > Development & Technical Discussion > Why was the 6th ServiceFlags bit skipped?
 « previous topic next topic »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!