The Hello message is the first message sent between the Gateway and a relay. The Hello message is used to inform a peer of the sender’s protocol version, network number, buffer and node ID.
The ACK Message is sent to acknowledge the receipt of a hello message. The ACK message does not include a payload.
A Keep-alive message that should expect a Pong Message response with the provided nonce.
Response to the Ping Message that should include the nonce provided in the Ping message.
Message used to broadcast a new block to the BDN.
Message to propagate a transaction across the BDN.
Message used to request information about services with specified short IDs.
Message with tx details send in response to GET_TRANSACTIONS Message.
A transaction info object is a part of the Transactions Message that describes a single transaction and its associated short ID.
A key message includes the encryption key used to encrypt a block when encryption is used for blocks sent over the BDN.
Request for other Gateways to hold onto the block for a timeout to avoid encrypted block duplication.
Request for the Gateway to disconnect from it’s Relay peers. This message does not have a payload.
Provides expired transactions for removal from Gateway memory. The expired transactions may be provided as a list of short IDs or as a list of transaction hashes. Since Gateways are not validating nodes, over time they will collect transactions that have been discarded by blockchain network full nodes. This may occur because, for example, the transaction was invalid, double spent, or provided insufficient fees. The bloXroute BDN will occasionally poll its internal blockchain nodes for a list of valid transactions and compare it to its list of tracked transactions. Transactions not found in internal blockchain nodes will be broadcast to the network with the Transaction Cleanup message to permit Gateways to remove these transactions from their memory.