Bitcoin Optech Newsletter #426

What happened

With a new set324alias message, a node announces its own aliases at connection time, so new messages can be deployed and experimented with at the P2P (machines connecting directly to each other, with no server in between) layer without that coordination. Towns also noted that the space saving ranges from up to 66% on a connection carrying only pings to about 5% on a typical connection, and is zero until new messages without an existing one-byte ID are deployed.

News ● Dynamic one-byte message type IDs for BIP324: Anthony Towns posted to the Bitcoin-Dev mailing list a draft BIP that lets each peer choose its own one-byte message type IDs for the messages it sends over the v2 P2P transport . ● Discussion of conventions for tagged hash tags in BIPs: Fabian Jahr posted to the Bitcoin-Dev mailing list asking whether BIPs that use BIP340 tagged hashes should include the BIP number in the tag.

BIPs 324, 340, 352, 374, and 445 do, while BIP327 and BIP341 use descriptive names such as “TapLeaf”. It aims to do so without requiring trusted operators, interactivity, or liveness dependencies.