From: Peter Todd <pete@petertodd.org>
To: Anthony Towns <aj@erisian.com.au>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Proposal] BIP324 One-Byte Message Type ID Alias Assignment
Date: Sun, 20 Sep 2026 08:29:31 +0000 [thread overview]
Message-ID: <aq-Za9yiCcwQKhPu@petertodd.org> (raw)
In-Reply-To: <aq9ADn7GscMHWc19@erisian.com.au>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-09-20 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 2:08 [bitcoindev] [BIP Proposal] BIP324 One-Byte Message Type ID Alias Assignment Anthony Towns
2026-09-20 8:29 ` Peter Todd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aq-Za9yiCcwQKhPu@petertodd.org \
--to=pete@petertodd.org \
--cc=aj@erisian.com.au \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox