From a3370b5c9d4973c52a2b447267ec03f3ef4303c3 Mon Sep 17 00:00:00 2001 From: Anthony Towns Date: Fri, 30 Jan 2026 16:02:05 +1000 Subject: [PATCH 1/3] BIP 324: Add auxiliary file tracking assignments of one-byte message type IDs --- bip-0324.mediawiki | 6 ++++-- bip-0324/message_type_ids.md | 16 ++++++++++++++++ 2 files changed, 20 insertions(+), 2 deletions(-) create mode 100644 bip-0324/message_type_ids.md diff --git a/bip-0324.mediawiki b/bip-0324.mediawiki index 4e9d26a8..e0bdd8a5 100644 --- a/bip-0324.mediawiki +++ b/bip-0324.mediawiki @@ -10,7 +10,7 @@ Type: Specification Assigned: 2019-03-08 License: BSD-3-Clause - Version: 1.0.1 + Version: 1.0.2 Replaces: 151 @@ -573,7 +573,7 @@ The following table lists currently defined message type IDs and the 12-byte ASC When a message type has both a 1-byte encoding and a 13-byte encoding defined, peers that support receiving that message type should accept messages using either encoding (e.g., if the "getblocktxn" message type is supported, then both the 1-byte b'\x0a' encoding and the 13-byte b'\x00getblocktxn\x00' should be supported, and behavior should not depend on which of the two encodings is received). -Additional message type IDs may be added separately after BIP finalization. +Additional message type IDs may be defined by other BIPs. They should be added to the [[bip-0324/message_type_ids.md|message type IDs table]] to ease coordination. === Signaling specification === ==== Signaling v2 support ==== @@ -589,6 +589,8 @@ For development and testing purposes, we provide a collection of test vectors in == Changelog == + * 1.0.2 (2026-01-30) + * Add message type ID table in auxiliary file * 1.0.1 (2026-01-16) * Specify equivalence of 1-byte and 13-byte `message_type` * 1.0.0 (2024-07-10) diff --git a/bip-0324/message_type_ids.md b/bip-0324/message_type_ids.md new file mode 100644 index 00000000..09faaae6 --- /dev/null +++ b/bip-0324/message_type_ids.md @@ -0,0 +1,16 @@ + +# One-byte message type allocations + +This table lists additional message type IDs that various BIPs have +assigned or proposed for assignment. + +Type | Message | Proposal +---- | ------------ | -------- + n/a | n/a | (none listed yet) + +Note that this table is not authoritative but instead is reflective +of the BIPs proposing the changes. If multiple BIPs make conflicting +assignments for message type IDs, that may lead to multiple entries for +the same message type ID in this table. BIPs that are in Draft status +may be included in the table, and as a result, the IDs and messages they +define may be changed in future. From df1f098a8b157e7447bb821e740107d55a201b5b Mon Sep 17 00:00:00 2001 From: Anthony Towns Date: Sat, 31 Jan 2026 17:21:07 +1000 Subject: [PATCH 2/3] BIP324, BIP183: Add utreexo's p2pv2 message type ids --- bip-0324/message_type_ids.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/bip-0324/message_type_ids.md b/bip-0324/message_type_ids.md index 09faaae6..d0e0ef5e 100644 --- a/bip-0324/message_type_ids.md +++ b/bip-0324/message_type_ids.md @@ -6,7 +6,14 @@ assigned or proposed for assignment. Type | Message | Proposal ---- | ------------ | -------- - n/a | n/a | (none listed yet) + 29 | uproof | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923) + 30 | getuproof | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923) + 31 | uttls | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923) + 32 | getuttls | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923) + 33 | usummary | [BIP 183 / PR#1923](https://github.com/bitcoin/bips/pull/1923) + 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) Note that this table is not authoritative but instead is reflective of the BIPs proposing the changes. If multiple BIPs make conflicting From a50c0ea32b104832d15b10a3d65bc77ee8df98da Mon Sep 17 00:00:00 2001 From: Anthony Towns Date: Sat, 31 Jan 2026 17:25:09 +1000 Subject: [PATCH 3/3] BIP324, BIP434: Assign message type id for "feature" message --- bip-0324/message_type_ids.md | 1 + bip-0434.md | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/bip-0324/message_type_ids.md b/bip-0324/message_type_ids.md index d0e0ef5e..4ececd20 100644 --- a/bip-0324/message_type_ids.md +++ b/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) Note that this table is not authoritative but instead is reflective of the BIPs proposing the changes. If multiple BIPs make conflicting diff --git a/bip-0434.md b/bip-0434.md index 3cf53995..80d94b92 100644 --- a/bip-0434.md +++ b/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