From: "'Sjors Provoost' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Fabian <fjahr@protonmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Convention for tagged hash tags in BIPs
Date: Tue, 29 Sep 2026 12:03:09 +0200 [thread overview]
Message-ID: <6F40C103-063B-46F1-9D7F-3C9D0B778879@sprovoost.nl> (raw)
In-Reply-To: <dxapm4DOcrDL6_oCYSqBAdFP0fAQA9IHInRzzTuCeWVYD2Xd0ynPsTa8hYEcRFOYQPnvoQK15TtK6oAZBfa-4b5DbIuFemSFGVifxGTLOlc=@protonmail.com>
Hi Fabian,
> Op 22 sep 2026, om 11:07 heeft 'Fabian' via Bitcoin Development Mailing List <bitcoindev@googlegroups.com> het volgende geschreven:
>
> Hi all,
>
> while reviewing BIP 459 (DahLIAS) theStack pointed out to me
> that most recent cryptography BIPs put the BIP number into
> their tagged hash tags but that some others use a
> descriptive name instad.
[...]
> As far as I can tell there is no written rule and the
> existing BIPs are inconsistent. BIP 324, 340, 352, 374 and
> 445 include the number.
BIP138 also includes the number. [0]
> ...against including the number:
> - The spec is broken at the time the number is assigned,
> requiring extra work on all implementation sites that
> already exist.
This was a bit annoying, since all test vectors had to be regenerated once
the number was assigned. But it's really not a big deal, and other
modifications to the spec also required this.
- Sjors
[0] https://github.com/bitcoin/bips/blob/master/bip-0138.md
--
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/6F40C103-063B-46F1-9D7F-3C9D0B778879%40sprovoost.nl.
prev parent reply other threads:[~2026-09-29 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 9:07 [bitcoindev] Convention for tagged hash tags in BIPs 'Fabian' via Bitcoin Development Mailing List
2026-09-29 10:03 ` 'Sjors Provoost' via Bitcoin Development Mailing List [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=6F40C103-063B-46F1-9D7F-3C9D0B778879@sprovoost.nl \
--to=bitcoindev@googlegroups.com \
--cc=fjahr@protonmail.com \
--cc=sjors@sprovoost.nl \
/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