From: Zeeshan Ali Khan <zeenix@gmail.com>
To: Hans Stringuer <hans.stringuer@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] BIP Draft Post-Quantum Address Format (bc1z) using ML-DSA-65
Date: Fri, 13 Nov 2026 16:49:49 +0100 [thread overview]
Message-ID: <CAAa3hFN+z1KGRkU_8JLmQ_1cXMZEYHO-0370Q_REv_MB2ci9Og@mail.gmail.com> (raw)
In-Reply-To: <9463348c-b2ec-4c6f-b9ec-2e9e2fc7d105n@googlegroups.com>
Hi Hans,
> 5. Whether the community sees value in pursuing this before a CRQC exists
I can't speak for others but I think this is definitely useful
**before** a CRQC exists. It'd be too late for the 6.9 million BTC you
mentioned when there is CRQC. :)
> revealing the full public key only at spend time in the witness — similar to how P2WPKH works today.
I think it'd be useful to highlight that unlike a P2WPKH address, the
address remains quantum-resistant even after its public key and
signatures are revealed.
--
Regards,
Zeeshan Ali Khan
--
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/CAAa3hFN%2Bz1KGRkU_8JLmQ_1cXMZEYHO-0370Q_REv_MB2ci9Og%40mail.gmail.com.
next prev parent reply other threads:[~2026-11-13 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 17:25 [bitcoindev] BIP Draft Post-Quantum Address Format (bc1z) using ML-DSA-65 Hans Stringuer
2026-11-13 12:18 ` [bitcoindev] " Hans Stringuer
2026-11-13 15:49 ` Zeeshan Ali Khan [this message]
2026-11-13 17:25 ` [bitcoindev] " Hans Stringuer
2026-11-13 20:16 ` Murch
2026-11-13 20:29 ` Hans Stringuer
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=CAAa3hFN+z1KGRkU_8JLmQ_1cXMZEYHO-0370Q_REv_MB2ci9Og@mail.gmail.com \
--to=zeenix@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=hans.stringuer@gmail.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