Bitcoin protocol message types. More...

Variables
const char *	VERSION ="version"
	The version message provides information about the transmitting node to the receiving node at the beginning of a connection. More...

const char *	VERACK ="verack"
	The verack message acknowledges a previously-received version message, informing the connecting node that it can begin to send other messages. More...

const char *	ADDR ="addr"
	The addr (IP address) message relays connection information for peers on the network. More...

const char *	INV ="inv"
	The inv message (inventory message) transmits one or more inventories of objects known to the transmitting peer. More...

const char *	GETDATA ="getdata"
	The getdata message requests one or more data objects from another node. More...

const char *	MERKLEBLOCK ="merkleblock"
	The merkleblock message is a reply to a getdata message which requested a block using the inventory type MSG_MERKLEBLOCK. More...

const char *	GETBLOCKS ="getblocks"
	The getblocks message requests an inv message that provides block header hashes starting from a particular point in the block chain. More...

const char *	GETHEADERS ="getheaders"
	The getheaders message requests a headers message that provides block headers starting from a particular point in the block chain. More...

const char *	TX ="tx"
	The tx message transmits a single transaction. More...

const char *	HEADERS ="headers"
	The headers message sends one or more block headers to a node which previously requested certain headers with a getheaders message. More...

const char *	BLOCK ="block"
	The block message transmits a single serialized block. More...

const char *	GETADDR ="getaddr"
	The getaddr message requests an addr message from the receiving node, preferably one with lots of IP addresses of other receiving nodes. More...

const char *	MEMPOOL ="mempool"
	The mempool message requests the TXIDs of transactions that the receiving node has verified as valid but which have not yet appeared in a block. More...

const char *	PING ="ping"
	The ping message is sent periodically to help confirm that the receiving peer is still connected. More...

const char *	PONG ="pong"
	The pong message replies to a ping message, proving to the pinging node that the ponging node is still alive. More...

const char *	NOTFOUND ="notfound"
	The notfound message is a reply to a getdata message which requested an object the receiving node does not have available for relay. More...

const char *	FILTERLOAD ="filterload"
	The filterload message tells the receiving peer to filter all relayed transactions and requested merkle blocks through the provided filter. More...

const char *	FILTERADD ="filteradd"
	The filteradd message tells the receiving peer to add a single element to a previously-set bloom filter, such as a new public key. More...

const char *	FILTERCLEAR ="filterclear"
	The filterclear message tells the receiving peer to remove a previously-set bloom filter. More...

const char *	REJECT ="reject"
	The reject message informs the receiving node that one of its previous messages has been rejected. More...

const char *	SENDHEADERS ="sendheaders"
	Indicates that a node prefers to receive new block announcements via a "headers" message rather than an "inv". More...

const char *	FEEFILTER ="feefilter"
	The feefilter message tells the receiving peer not to inv us any txs which do not meet the specified min fee rate. More...

const char *	SENDCMPCT ="sendcmpct"
	Contains a 1-byte bool and 8-byte LE version number. More...

const char *	CMPCTBLOCK ="cmpctblock"
	Contains a CBlockHeaderAndShortTxIDs object - providing a header and list of "short txids". More...

const char *	GETBLOCKTXN ="getblocktxn"
	Contains a BlockTransactionsRequest Peer should respond with "blocktxn" message. More...

const char *	BLOCKTXN ="blocktxn"
	Contains a BlockTransactions. More...

Detailed Description

Bitcoin protocol message types.

When adding new message types, don't forget to update allNetMessageTypes in protocol.cpp.

Variable Documentation

◆ ADDR

const char * NetMsgType::ADDR ="addr"

The addr (IP address) message relays connection information for peers on the network.

See also: https://bitcoin.org/en/developer-reference#addr

Definition at line 20 of file protocol.cpp.

◆ BLOCK

const char * NetMsgType::BLOCK ="block"

The block message transmits a single serialized block.

See also: https://bitcoin.org/en/developer-reference#block

Definition at line 28 of file protocol.cpp.

◆ BLOCKTXN

const char * NetMsgType::BLOCKTXN ="blocktxn"

Contains a BlockTransactions.

Sent in response to a "getblocktxn" message.

Since: protocol version 70014 as described by BIP 152

Definition at line 43 of file protocol.cpp.

◆ CMPCTBLOCK

const char * NetMsgType::CMPCTBLOCK ="cmpctblock"

Contains a CBlockHeaderAndShortTxIDs object - providing a header and list of "short txids".

Since: protocol version 70014 as described by BIP 152

Definition at line 41 of file protocol.cpp.

◆ FEEFILTER

const char * NetMsgType::FEEFILTER ="feefilter"

The feefilter message tells the receiving peer not to inv us any txs which do not meet the specified min fee rate.

Since: protocol version 70013 as described by BIP133

Definition at line 39 of file protocol.cpp.

◆ FILTERADD

const char * NetMsgType::FILTERADD ="filteradd"

The filteradd message tells the receiving peer to add a single element to a previously-set bloom filter, such as a new public key.

Since: protocol version 70001 as described by BIP37. Only available with service bit NODE_BLOOM since protocol version 70011 as described by BIP111.

See also: https://bitcoin.org/en/developer-reference#filteradd

Definition at line 35 of file protocol.cpp.

◆ FILTERCLEAR

const char * NetMsgType::FILTERCLEAR ="filterclear"

The filterclear message tells the receiving peer to remove a previously-set bloom filter.

Since: protocol version 70001 as described by BIP37. Only available with service bit NODE_BLOOM since protocol version 70011 as described by BIP111.

See also: https://bitcoin.org/en/developer-reference#filterclear

Definition at line 36 of file protocol.cpp.

◆ FILTERLOAD

const char * NetMsgType::FILTERLOAD ="filterload"

The filterload message tells the receiving peer to filter all relayed transactions and requested merkle blocks through the provided filter.

Since: protocol version 70001 as described by BIP37. Only available with service bit NODE_BLOOM since protocol version 70011 as described by BIP111.

See also: https://bitcoin.org/en/developer-reference#filterload

Definition at line 34 of file protocol.cpp.

◆ GETADDR

const char * NetMsgType::GETADDR ="getaddr"

The getaddr message requests an addr message from the receiving node, preferably one with lots of IP addresses of other receiving nodes.

See also: https://bitcoin.org/en/developer-reference#getaddr

Definition at line 29 of file protocol.cpp.

◆ GETBLOCKS

const char * NetMsgType::GETBLOCKS ="getblocks"

The getblocks message requests an inv message that provides block header hashes starting from a particular point in the block chain.

See also: https://bitcoin.org/en/developer-reference#getblocks

Definition at line 24 of file protocol.cpp.

◆ GETBLOCKTXN

const char * NetMsgType::GETBLOCKTXN ="getblocktxn"

Contains a BlockTransactionsRequest Peer should respond with "blocktxn" message.

Since: protocol version 70014 as described by BIP 152

Definition at line 42 of file protocol.cpp.

◆ GETDATA

const char * NetMsgType::GETDATA ="getdata"

The getdata message requests one or more data objects from another node.

See also: https://bitcoin.org/en/developer-reference#getdata

Definition at line 22 of file protocol.cpp.

◆ GETHEADERS

const char * NetMsgType::GETHEADERS ="getheaders"

The getheaders message requests a headers message that provides block headers starting from a particular point in the block chain.

Since: protocol version 31800.

See also: https://bitcoin.org/en/developer-reference#getheaders

Definition at line 25 of file protocol.cpp.

◆ HEADERS

const char * NetMsgType::HEADERS ="headers"

The headers message sends one or more block headers to a node which previously requested certain headers with a getheaders message.

Since: protocol version 31800.

See also: https://bitcoin.org/en/developer-reference#headers

Definition at line 27 of file protocol.cpp.

◆ INV

const char * NetMsgType::INV ="inv"

The inv message (inventory message) transmits one or more inventories of objects known to the transmitting peer.

See also: https://bitcoin.org/en/developer-reference#inv

Definition at line 21 of file protocol.cpp.

◆ MEMPOOL

const char * NetMsgType::MEMPOOL ="mempool"

The mempool message requests the TXIDs of transactions that the receiving node has verified as valid but which have not yet appeared in a block.

Since: protocol version 60002.

See also: https://bitcoin.org/en/developer-reference#mempool

Definition at line 30 of file protocol.cpp.

◆ MERKLEBLOCK

const char * NetMsgType::MERKLEBLOCK ="merkleblock"

The merkleblock message is a reply to a getdata message which requested a block using the inventory type MSG_MERKLEBLOCK.

Since: protocol version 70001 as described by BIP37.

See also: https://bitcoin.org/en/developer-reference#merkleblock

Definition at line 23 of file protocol.cpp.

◆ NOTFOUND

const char * NetMsgType::NOTFOUND ="notfound"

The notfound message is a reply to a getdata message which requested an object the receiving node does not have available for relay.

Since: protocol version 70001.

See also: https://bitcoin.org/en/developer-reference#notfound

Definition at line 33 of file protocol.cpp.

◆ PING

const char * NetMsgType::PING ="ping"

The ping message is sent periodically to help confirm that the receiving peer is still connected.

See also: https://bitcoin.org/en/developer-reference#ping

Definition at line 31 of file protocol.cpp.

◆ PONG

const char * NetMsgType::PONG ="pong"

The pong message replies to a ping message, proving to the pinging node that the ponging node is still alive.

Since: protocol version 60001 as described by BIP31.

See also: https://bitcoin.org/en/developer-reference#pong

Definition at line 32 of file protocol.cpp.

◆ REJECT

const char * NetMsgType::REJECT ="reject"

The reject message informs the receiving node that one of its previous messages has been rejected.

Since: protocol version 70002 as described by BIP61.

See also: https://bitcoin.org/en/developer-reference#reject

Definition at line 37 of file protocol.cpp.

◆ SENDCMPCT

const char * NetMsgType::SENDCMPCT ="sendcmpct"

Contains a 1-byte bool and 8-byte LE version number.

Indicates that a node is willing to provide blocks via "cmpctblock" messages. May indicate that a node prefers to receive new block announcements via a "cmpctblock" message rather than an "inv", depending on message contents.

Since: protocol version 70014 as described by BIP 152

Definition at line 40 of file protocol.cpp.

◆ SENDHEADERS

const char * NetMsgType::SENDHEADERS ="sendheaders"

Indicates that a node prefers to receive new block announcements via a "headers" message rather than an "inv".

Since: protocol version 70012 as described by BIP130.

See also: https://bitcoin.org/en/developer-reference#sendheaders

Definition at line 38 of file protocol.cpp.

◆ TX

const char * NetMsgType::TX ="tx"

The tx message transmits a single transaction.

See also: https://bitcoin.org/en/developer-reference#tx

Definition at line 26 of file protocol.cpp.

◆ VERACK

const char * NetMsgType::VERACK ="verack"

The verack message acknowledges a previously-received version message, informing the connecting node that it can begin to send other messages.

See also: https://bitcoin.org/en/developer-reference#verack

Definition at line 19 of file protocol.cpp.

◆ VERSION

const char * NetMsgType::VERSION ="version"

The version message provides information about the transmitting node to the receiving node at the beginning of a connection.

See also: https://bitcoin.org/en/developer-reference#version

Definition at line 18 of file protocol.cpp.

Variables