From: PYM <pywebdesign@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] A slight change proposed on Committing to quantum resistance: a slow defence for Bitcoin against a fast quantum computing attack
Date: Mon, 6 Apr 2026 13:30:33 -0700 (PDT) [thread overview]
Message-ID: <4303fca1-81a8-4655-ac53-33f566daebc2n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2011 bytes --]
Hello, here's a small idea to combine merkel tree with timestamped message
signature to bind p2pkh adress to quantum resistant scheme so user do not
need to rush to move bitcoin before qday, in a space efficient form.
- *Universal P2PKH freeze* — At a defined block height, all P2PKH outputs
become unspendable via classical ECDSA.
- *Pre-freeze claim* — Before the freeze, owners sign a claim containing
their Bitcoin address and a new post-quantum public key of their choice.
The claim is ECDSA-signed, proving classical ownership while quantum
computers don't yet exist.
- *Merkle-batched publication* — Claims are batched into Merkle trees. Only
the 32-byte root goes on-chain via OP_RETURN. One transaction covers large
amount of claims.
- *Post-freeze spending* — To spend a frozen output, provide: the original
claim, a Merkle inclusion proof linking it to a pre-freeze root, and a
signature from the post-quantum key committed in the claim.
- *No claim, no spend* — Any P2PKH output with no registered claim before
the freeze height is permanently frozen until a future recovery mechanism
is defined by the community.
I do not have enough knowledge to find the ideal scheme or implementation
that fulfill those requirements sadly.
1 - Stewart I, Ilie D, Zamyatin A, Werner S, Torshizi MF, Knottenbelt WJ.
Committing to quantum resistance: a slow defence for Bitcoin against a fast
quantum computing attack. R Soc Open Sci. 2018 Jun 20;5(6):180410. doi:
10.1098/rsos.180410. PMID: 30110420; PMCID: PMC6030263.
https://pmc.ncbi.nlm.nih.gov/articles/PMC6030263/
--
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/4303fca1-81a8-4655-ac53-33f566daebc2n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2762 bytes --]
reply other threads:[~2026-04-06 20:32 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=4303fca1-81a8-4655-ac53-33f566daebc2n@googlegroups.com \
--to=pywebdesign@gmail.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