From: "'Ava Chow' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Descriptors using H as a hardened indicator
Date: Mon, 23 Jun 2025 18:37:52 +0000 [thread overview]
Message-ID: <848d3d4b-94a5-4e7c-b178-62cf5015b65f@achow101.com> (raw)
Hi All,
Recently someone pointed out that BIP 380 specifies that `H` can be used
as a hardened indicator in derivation paths, in addition to `'` and `h`.
However, there was also a test which suggested that `H` was not a valid
hardened indicator. A PR resolving this discrepancy by moving that test
from the invalid to the valid section was merged, but there is still a
question of whether this was the right course of action.
Currently, Bitcoin Core does not implement this, and AFAICT, neither
does rust-miniscript. There is an open PR to Bitcoin Core to allow `H`
(https://github.com/bitcoin/bitcoin/pull/32788), but ongoing discussion
suggests that perhaps the BIP should be modified instead as it seems
probable that no implementation of descriptors allows `H`.
So the question is: are there any implementations of descriptors that
emit descriptors that use `H` as a hardened indicator, or permit `H` as
a hardened indicator?
I think the former question is more useful to know as it is more
important that the descriptor implementations can parse each other's
products. It is possible that there are implementations that allow `H`
but do not emit `H`, since there are libraries that provide BIP 32
utilities which allow `H`.
Thanks
Ava
--
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/848d3d4b-94a5-4e7c-b178-62cf5015b65f%40achow101.com.
reply other threads:[~2025-06-23 18:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=848d3d4b-94a5-4e7c-b178-62cf5015b65f@achow101.com \
--to=bitcoindev@googlegroups.com \
--cc=lists@achow101.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