From: Jean Pablo <jeanpablo.jp@hotmail.com>
To: "bitcoindev@googlegroups.com" <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] rawtr() Output Script Descriptors
Date: Thu, 6 Aug 2026 13:51:55 +0000 [thread overview]
Message-ID: <DD9687EA-368C-482F-91B6-C5E2E230830C@hotmail.com> (raw)
The rawtr() descriptor has been in Bitcoin Core since 24.0, but it was
never specified in a BIP. Pieter noted this on the bips repo back in
March [0] and nobody picked it up, so I wrote a draft:
https://github.com/jeanpablojp/bips/blob/rawtr-descriptor/bip-rawtr.mediawiki
BIP 390 only allows musig() inside tr(), rawtr() or sp(), and two of
its test vectors are rawtr() descriptors, so there's a published BIP
depending on an expression no BIP defines. Outside the repo people
fill the blank by guessing: bdk-ffi's test suite cites rawtr as
BIP-386, which doesn't mention it.
The draft follows the shape of BIPs 384 and 385. Test vectors were
generated against Bitcoin Core master with getdescriptorinfo and
deriveaddresses. The first vector reuses the key from the first tr()
vector of BIP 386: same key, different script, because rawtr()
applies no tweak. The musig() vectors come from BIP 390 verbatim.
Scope is rawtr(KEY) only. The partial-descriptor ideas (rawnode(),
rawleaf()) have their own design discussion in bips PR 1721 and I'm
not touching them here.
On structure: Appendix B of BIP 380 has been one BIP per expression
group so far, and musig() and sp() both got their own numbers this
year, so I drafted it as a separate BIP rather than a new section in
386.
Feedback welcome.
[0] https://github.com/bitcoin/bips/pull/2050#issuecomment-3986205616
--
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/DD9687EA-368C-482F-91B6-C5E2E230830C%40hotmail.com.
reply other threads:[~2026-08-06 13:59 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=DD9687EA-368C-482F-91B6-C5E2E230830C@hotmail.com \
--to=jeanpablo.jp@hotmail.com \
--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