Structs
The response to
GetBlockBodies, containing the block bodies that the peer knows about if
any were found.A block hash and a block number.
The response to
GetBlockHeaders, containing headers if any headers were found.Filter that describes the state of blockchain and can be used to check incoming
ForkIds for compatibility.CRC32 hash of all previous forks starting from genesis block.A fork identifier as defined by EIP-2124.
Serves as the chain compatibility identifier.
A request for a peer to return block bodies for the given block hashes.
A request for a peer to return block headers starting at the requested block.
The peer must return at most
limit headers.
If the reverse field is true, the headers will be returned starting
at start_block, traversing towards the genesis block.
Otherwise, headers will be returned starting at start_block,
traversing towards the latest block.A request for state tree nodes corresponding to the given hashes.
This message was removed in
eth/67, only clients running eth/66 or earlier will respond to
this message.A list of transaction hashes that the peer would like transaction bodies for.
A request for transaction receipts from the given block hashes.
A new block with the current total difficulty, which includes the difficulty of the returned
block.
This informs peers of new blocks that have appeared on the network.
This informs peers of transaction hashes for transactions that have appeared on the network,
but have not been included in a block.
The response to
GetNodeData, containing the state tree nodes or contract bytecode
corresponding to the requested hashes.The response to
GetPooledTransactions, containing the transaction bodies associated with
the requested hashes.An
eth protocol message, containing a message ID and payload.The response to
GetReceipts, containing receipt lists that correspond to each block
requested.This is used for all request-response style
eth protocol messages.
This can represent either a request or a response, since both include a message payload and
request id.The status message is used in the eth protocol handshake to ensure that peers are on the same
network and are following the same fork.
The total difficulty and best block hash are used to identify whether or not the requesting
client should be sent historical blocks for a full blockchain sync.
This informs peers of transactions that have appeared on the network and are not yet included
in a block.
Enums
Either a block hash or a block number
Represents a message in the eth wire protocol, versions 66 and 67.
Represents message IDs for eth protocol messages.
The
eth protocol version.An ethereum network request for version 66.
An ethereum network response for version 66.