XVERSION
login
{ "title":"XVERSION", "related":["/protocol","/protocol/p2p/xupdate","/protocol/p2p/xversionkeys"] }

Notifies peers about a protocol configuration value

This message notifies a peer about extended protocol parameters. This message MAY be sent during connection initialization. If sent, it MUST be sent immediately subsequent to the receipt of the VERACK message, and before other non-initialization messages are sent.

compact int compact int variable bytes compact int variable bytes
vector size N of key 1 value 1 vector of bytes key N value N vector of bytes

The value is a vector of bytes. These bytes can be an object that is itself serialized, but MUST exist within the vector “envelope” so that implementations that do not recognize a field can skip it. The serialization format of the bytes inside the “envelope” is defined by the creator of the key, however, Bitcoin P2P network serialization is recommended since it is also used to encode/decode all the messages of this protocol.

See XVERSION specification for additional details.

XVERSION Fields

XVERSION field identifiers are 32 bits and split into a 16 bit prefix and 16 bit suffix. Each development group is assigned a prefix so that new identifiers do not accidentally conflict. Once a field identifier is created by group A, it should be used by other software both to receive that information from A and to present that information to other software. Therefore, group A MUST NOT change the syntax or semantics of a field once defined. To change a field, create a new identifier and deprecate (by no longer using the original identifier).

Prefix and Suffix Assignments

See xversionkeys for a full list of assigned prefixes and field definitions.

Support

Supported by: Bitcoin Unlimited