On Sun, Sep 20, 2026 at 12:08:14PM +1000, Anthony Towns wrote:
> Hello world,
> 
> I'd like to propose adding a `set324alias` p2p message for dynamic
> assignment of BIP324 one-byte message type IDs for P2P messages.
> 
> You can see the current (non-dynamic) assignments at:
> 
>  - https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki#user-content-v2_Bitcoin_P2P_message_structure
>  - https://github.com/bitcoin/bips/blob/master/bip-0324/message_type_ids.md
> 
> The TLDR summary is that nodes that implement this proposal would send a
> `set324alias [98:messagea, 99:messageb]` message, then afterwards can
> save 12 bytes every time they send `messagea` or `messageb` by using
> the corresponding one-byte message type id (98 or 99) instead. Which
> messages get aliases and what those number those aliases have are
> chosen by whoever sends the messages (probably by the node developer
> at compile-time), so nodes on the same connection may give different
> aliases to the same messages.
> 
> Draft BIP text follows, including a link to a bitcoin core patchset
> implementing it.

I think the BIP needs to include within it an estimate of what % of
total bandwidth this might actually save.

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/aq-Za9yiCcwQKhPu%40petertodd.org.