BitcoinCash/specification
1
Fork 0
Code Issues Pull Requests Releases Activity

wiki commit

Browse Source
This commit is contained in:
bitcoin
2019-12-03 16:31:23 -05:00
committed by buwiki
parent 35963aa9ef
commit 25bcd8a376
1 changed files with 12 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
protocol/network/messages/version.md
+12 -5
View File
@@ -18,6 +18,9 @@ The services field is an 8 byte little-endian-serialized bitfield that described
* 5: NODE_BITCOIN_CASH
The node supports the BCH chain. This is intended to be just a temporary service bit until the BTC/BCH fork actually happens.
* 24-31: Reserved for experimental changes
These bits are reserved for temporary experiments. Just pick a bit that isn't getting used, or one not being used much, and notify the community. Remember that service bits are just unauthenticated advertisements, so your code must be robust against collisions and other cases where nodes may be advertising a service they do not actually support.
### Node Specific Messages
#### Bitcoin XT
@@ -25,7 +28,6 @@ The services field is an 8 byte little-endian-serialized bitfield that described
* 1: NODE_GETUTXO <img src="/_static_/images/warning.png">
The node is capable of responding to the getutxo protocol request. See [BIP 64](https://github.com/bitcoin/bips/blob/master/bip-0064.mediawiki) for details on how this is implemented. *Supported by Bitcoin XT only*
#### Bitcoin Unlimited
* 4: NODE_XTHIN <img src="/_static_/images/warning.png">
@@ -36,6 +38,14 @@ The services field is an 8 byte little-endian-serialized bitfield that described
The node supports Graphene blocks. If this is turned off then the node will not service graphene requests nor make graphene requests.
*Supported by Bitcoin Unlimited only*
#### Bitcoin Verde
* 7: BLOCKCHAIN_INDEX_ENABLED <img src="/_static_/images/warning.png">
Indicates that the node is an indexing node and supports returning information custom to the requesting user's addresses.
* 8: SLP_INDEX_ENABLED <img src="/_static_/images/warning.png">
Indicates that the node tracks Simple Ledger Protocol validity and supports returning this status for individual transactions.
#### Proposed
* 7: NODE_WEAKBLOCKS <img src="/_static_/images/warning.png">
@@ -45,7 +55,4 @@ The services field is an 8 byte little-endian-serialized bitfield that described
Indicates the node is capable of serving compact block filters to SPV clients, AKA the "Neutrino" protocol ([BIP157](https://github.com/bitcoin/bips/blob/master/bip-0157.mediawiki), and [BIP158](https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki)).
* 9: NODE_NETWORK_LIMITED <img src="/_static_/images/warning.png">
This means the same as NODE_NETWORK with the limitation of only serving a small subset of the blockchain. See [BIP159](https://github.com/bitcoin/bips/blob/master/bip-0159.mediawiki) for details on how this is implemented.
* 24-31: Experimental <img src="/_static_/images/warning.png">
These bits are reserved for temporary experiments. Just pick a bit that isn't getting used, or one not being used much, and notify the community. Remember that service bits are just unauthenticated advertisements, so your code must be robust against collisions and other cases where nodes may be advertising a service they do not actually support.
This means the same as NODE_NETWORK with the limitation of only serving a small subset of the blockchain. See [BIP159](https://github.com/bitcoin/bips/blob/master/bip-0159.mediawiki) for details on how this is implemented.