mirror of
https://github.com/bitcoin/bips.git
synced 2026-05-25 17:09:34 +00:00
BIP 324: Add auxiliary file tracking assignments of one-byte message type IDs
This commit is contained in:
@@ -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)
|
||||
|
||||
Reference in New Issue
Block a user