From: "'2099999997690000' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: "bitcoindev@googlegroups.com" <bitcoindev@googlegroups.com>
Subject: [bitcoindev] bitcoindev@googlegroups.com
Date: Wed, 09 Sep 2026 18:19:18 +0000 [thread overview]
Message-ID: <Sk4mSfbFO2smtuHSMyjmpjCrCIhHvnG7cajKVg6H6fx-H1MuS6gDxJxVyAiBXeg3IoSWgNevsE-xB41H0BsUHNcgUh-walxHAmA2vKIT-dE=@proton.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
Hi all,
Pursuant to the discussions about standardizing an unspendable NUMS key for an script path only taproot policy https://delvingbitcoin.org/t/unspendable-keys-in-descriptors/304 and https://github.com/bitcoin/bips/pull/1746 ; we undertook the issue with these guiding principles:
- We don't police adherence to other bips except when they directly affect the issue at hand.
- We use the already in place mechanisms in other bips.
- We don't claim semantic canonicalization of the script and only normalize the policy to some opinionated extent.
The gist is, we define _ as a placeholder for the unspendable NUMS key. We sort keys inside musig(...) and sortedmulti_a. We sort sibling pairs of the tree. If there is multipath extension, we add the same length tuple to the _ so that we don't fall to reuse. Then we pull the keys out and us @i placeholders and hash the whole thing consisting of the normalized descriptor and the keys. That would be the chain code for the H defined in BIP 341.
The details can be found here:
https://github.com/bitryonix/bips/blob/bip-xxxx-unspendable-internal-keys/bip-xxxx-unspendable-internal-keys.mediawiki
Best,
NTL
-
--
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/Sk4mSfbFO2smtuHSMyjmpjCrCIhHvnG7cajKVg6H6fx-H1MuS6gDxJxVyAiBXeg3IoSWgNevsE-xB41H0BsUHNcgUh-walxHAmA2vKIT-dE%3D%40proton.me.
[-- Attachment #2: Type: text/html, Size: 3574 bytes --]
reply other threads:[~2026-09-09 18:23 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='Sk4mSfbFO2smtuHSMyjmpjCrCIhHvnG7cajKVg6H6fx-H1MuS6gDxJxVyAiBXeg3IoSWgNevsE-xB41H0BsUHNcgUh-walxHAmA2vKIT-dE=@proton.me' \
--to=bitcoindev@googlegroups.com \
--cc=2099999997690000@proton.me \
/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