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: Mon, 14 Sep 2026 21:04:16 +0000 [thread overview]
Message-ID: <010001a0a1bc23e2-e1ac88ef-2f25-4561-ad02-11e943a2cda8-000000@email.amazonses.com> (raw)
In-Reply-To: <010001a06dd4cdd9-b8082042-8750-4e9a-917e-2053c919e4c4-000000@email.amazonses.com>
A short update: the draft is at v0.4.0.
Changes since the original post, with credit:
- v0.2.0: the derived condition now requires a complete spend recipe;
the partial-history UNDETERMINED rule is scoped to history-dependent
classifications; the aggregate-counter floor notes its conservative
over-approximation for revealed scripts that need no signature.
- v0.3.0, after conduition's review here: attacker-spendability is
distinguished from holder-provability, with the P2TR discussion
naming both questions. The EXPOSED_ON_SPEND naming problem is
recorded as open, EXPOSED_WHEN_SPENT the leading alternative.
- v0.4.0, after wallet feedback on Delving: the Abstract and
Motivation are rewritten to state the reasoning directly, opening
with the misclassification in my own tooling that started this.
Appendix A (informative) gives each level a fixed action key and a
one-line floor; wallets own the wording above it.
Draft, reference implementation and vectors:
https://github.com/duncan0k/pubkey-exposure-classification
I would still like to hear from anyone who considers this out of
scope for a BIP. Absent that, I intend to open a pull request against
bitcoin/bips in the coming weeks.
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/010001a0a1bc23e2-e1ac88ef-2f25-4561-ad02-11e943a2cda8-000000%40email.amazonses.com.
next prev parent reply other threads:[~2026-09-14 21:27 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 [this message]
2026-09-18 10:38 ` 'duncan0k' via Bitcoin Development Mailing List
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=010001a0a1bc23e2-e1ac88ef-2f25-4561-ad02-11e943a2cda8-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