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

BIP 324: Add auxiliary file tracking assignments of one-byte message type IDs

Browse Source
This commit is contained in:
Anthony Towns 2026-01-30 16:02:05 +10:00
parent 43e3983e4b
commit a3370b5c9d
2 changed files with 20 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bip-0324.mediawiki
View File

@ -10,7 +10,7 @@
Type: Specification
Assigned: 2019-03-08
License: BSD-3-Clause
Version: 1.0.1
Version: 1.0.2
Replaces: 151
</pre>
@ -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 <code>b'\x0a'</code> encoding and the 13-byte <code>b'\x00getblocktxn\x00'</code> 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)

16
bip-0324/message_type_ids.md Normal file
View File

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