From: Hunter Beast <hunter@surmount.systems>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Major BIP 360 Update
Date: Fri, 19 Dec 2025 12:45:43 -0800 (PST) [thread overview]
Message-ID: <7edb8e8f-064b-4409-9c6d-b4361c1e7df7n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1846 bytes --]
After reviewing community feedback, Ethan Heilman and I have enlisted the
help of a third co-author, Isabel Foxen Duke <https://x.com/isabelfoxenduke>,
in an editorial role to lead and execute a clean sheet rewrite of BIP 360.
Because previous revisions introduced meaningful technical changes, we
determined that a full rewrite, rather than incremental edits, was
warranted to improve clarity, internal coherence, and to better articulate
our intentions for managing potential quantum-related risks.
Consistent with its previous version, this proposal does not introduce
post-quantum signature schemes. Instead, BIP 360 proposes the addition of a
new output type with the key path spend removed, which is thus protected
from hypothetical breaks of Elliptic Curve Cryptography (ECC).
We have renamed this proposed output type "Pay-to-Tapscript-Hash (P2TSH)"
for clarity, and believe its adoption is an important first step in
protecting Bitcoin from potential threats to ECC, via quantum computers or
any other cryptanalytic advancements.
Additionally, the proposal now includes test vectors in Python and Rust.
With gratitude, we hope you’ll review these changes in the BIP Repo
<https://github.com/bitcoin/bips/pull/1670> or at BIP360.org
<http://bip360.org>. We look forward to ongoing community feedback, and new
ideas in our efforts to Make Bitcoin Quantum Resistant.
Thank you for your time,
Hunter Beast
--
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/7edb8e8f-064b-4409-9c6d-b4361c1e7df7n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 10393 bytes --]
next reply other threads:[~2025-12-20 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 20:45 Hunter Beast [this message]
2025-12-21 5:05 ` Erik Aronesty
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=7edb8e8f-064b-4409-9c6d-b4361c1e7df7n@googlegroups.com \
--to=hunter@surmount.systems \
--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