Browse Source

Pretty tables bring devs to the yard

master
Duke Leto 3 years ago
parent
commit
9881487c1b
  1. 32
      hip-0155.md

32
hip-0155.md

@ -43,30 +43,14 @@ fixed 16-byte IP address is replaced by a network ID and a variable-length addre
This means that the message contains a serialized <code>std::vector</code> of the following structure: This means that the message contains a serialized <code>std::vector</code> of the following structure:
!Type
!Name Type | Name | Description |
!Description -----|---------|-------------|
|- <code>uint32_t</code> | <code>time</code> | Time that this node was last seen as connected to the network. A time in Unix epoch time format. |
| <code>uint32_t</code> <code>CompactSize</code> | <code>services</code> | Service bits. A bit field that is 64 bits wide, encoded in [https://en.bitcoin.it/wiki/Protocol_documentation#Variable_length_integer CompactSize]. |
| <code>time</code> <code>uint8_t</code> | <code>networkID</code> | Network identifier. An 8-bit value that specifies which network is addressed. |
| Time that this node was last seen as connected to the network. A time in Unix epoch time format. <code>std::vector<uint8_t></code> | <code>addr</code> | Network address. The interpretation depends on networkID. |
|- <code>uint16_t</code> | <code>port</code> | Network port. If not relevant for the network this MUST be 0. |
| <code>CompactSize</code>
| <code>services</code>
| Service bits. A bit field that is 64 bits wide, encoded in [https://en.bitcoin.it/wiki/Protocol_documentation#Variable_length_integer CompactSize].
|-
| <code>uint8_t</code>
| <code>networkID</code>
| Network identifier. An 8-bit value that specifies which network is addressed.
|-
| <code>std::vector<uint8_t></code>
| <code>addr</code>
| Network address. The interpretation depends on networkID.
|-
| <code>uint16_t</code>
| <code>port</code>
| Network port. If not relevant for the network this MUST be 0.
|}
One message can contain up to 1,000 addresses. Clients SHOULD reject messages with more addresses. One message can contain up to 1,000 addresses. Clients SHOULD reject messages with more addresses.

Loading…
Cancel
Save