From: "'duncan0k' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Standardizing public key exposure classification for existing outputs
Date: Fri, 18 Sep 2026 10:38:48 +0000 [thread overview]
Message-ID: <010001a0b418f0f2-92c7e013-aea0-4707-ab25-06beafce173a-000000@email.amazonses.com> (raw)
In-Reply-To: <010001a06dd4cdd9-b8082042-8750-4e9a-917e-2053c919e4c4-000000@email.amazonses.com>
The draft is now at v0.5.1 and submitted to the BIPs repository as an
Informational BIP:
https://github.com/bitcoin/bips/pull/2294
Two things changed since the v0.4.0 note, both after murch's review on
Delving:
- The first two levels are now stated as BIP 360's long exposure and
short exposure vulnerabilities, per output, and the draft cites that
section as the source of the taxonomy.
- P2MR was wrong. My original post said a spend publishes key material
for every type except P2MR. That is false: a leaf spend puts the leaf
script, its Merkle path and a secp256k1 key in the mempool, the same
race as P2WSH. P2MR is EXPOSED_ON_SPEND until post-quantum leaves
exist, and NOT_EXPOSED has no member today.
Draft, reference implementation and 25 vectors:
https://github.com/duncan0k/pubkey-exposure-classification
Publication of an Informational BIP depends on feedback on the PR, so if
you have a view either way, that is where it counts.
duncan0k
--
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/010001a0b418f0f2-92c7e013-aea0-4707-ab25-06beafce173a-000000%40email.amazonses.com.
prev parent reply other threads:[~2026-09-18 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 19:10 [bitcoindev] Standardizing public key exposure classification for existing outputs 'duncan0k' via Bitcoin Development Mailing List
2026-09-07 20:53 ` 'conduition' via Bitcoin Development Mailing List
2026-09-08 3:53 ` 'duncan0k' via Bitcoin Development Mailing List
2026-09-14 21:04 ` 'duncan0k' via Bitcoin Development Mailing List
2026-09-18 10:38 ` 'duncan0k' 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=010001a0b418f0f2-92c7e013-aea0-4707-ab25-06beafce173a-000000@email.amazonses.com \
--to=bitcoindev@googlegroups.com \
--cc=duncan0k@cipherscope.io \
/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