BIP324, BIP434: Assign message type id for "feature" message

Author: ajtowns

bip-0324/message_type_ids.md

@@ -14,6 +14,7 @@ Type | Message      | Proposal
   34 | utreexotx    | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
   35 | uroot        | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
   36 | geturoot     | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923)
+  37 | feature      | [BIP 434](https://github.com/bitcoin/bips/blob/master/bip-0434.md) / [PR#2092](https://github.com/bitcoin/bips/pull/2092)
 
 Note that this table is not authoritative but instead is reflective
 of the BIPs proposing the changes. If multiple BIPs make conflicting

bip-0434.md

@@ -156,9 +156,11 @@ suffix covers part 3 of the BIP). For experimental features that do not
 chosen, such as a URL to the repository where development is taking place,
 or the sha256 digest of some longer reference.
 
+#### `feature` message 1-byte identifier
+
 Nodes implementing both this BIP and [BIP 324 (v2 P2P encrypted
 transport)][BIP324] MUST treat a message with a 1-byte `message_type`
-equal to `XXX` that is received prior to `verack` as the `feature` message.
+equal to `37` that is received prior to `verack` as the `feature` message.
 
 ### Feature negotiation