bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2026-02-09 15:23:09 +00:00
Code Issues Releases Wiki Activity

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

Browse Source
This commit is contained in:
Anthony Towns 2026-01-31 17:25:09 +10:00
parent df1f098a8b
commit a50c0ea32b
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
bip-0324/message_type_ids.md
View File

@ -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)
Note that this table is not authoritative but instead is reflective
of the BIPs proposing the changes. If multiple BIPs make conflicting

4
bip-0434.md
View File

@ -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