From: Peter Todd <pete@petertodd•org>
To: Jameson Lopp <jameson.lopp@gmail•com>
Cc: Antoine Riard <antoine.riard@gmail•com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: A Post Quantum Migration Proposal
Date: Sat, 19 Jul 2025 12:05:52 +0000 [thread overview]
Message-ID: <aHuKIKqvCZl5rcEX@petertodd.org> (raw)
In-Reply-To: <CADL_X_f3sDECRUosNaXyez3F_inKjJAWm=ESm3DSLCKD4JV7yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
On Mon, Jul 14, 2025 at 02:52:17PM -0400, Jameson Lopp wrote:
> Correct, this time is different in that we're not talking about vague
> unknown weaknesses. Rather, we're talking about a known algorithm that
> makes breaking cryptographic primitives orders of magnitude cheaper.
We already have known algorithms that would break cryptographic primitives if
sufficiently good analog computers actually existed. Or for that matter, "split
the universe" brute forcing. No-one is worried about them because "sufficiently
good" analog computers and multiverses are widely belived to not be physically
realizable.
For all the claims of progress on quantum computing hardware, the fact still
remains that no-one is even close to demonstrating cryptographic-relevant
quantum computing capabilities and the actual cryptographic-relevant
capabilities of real hardware are laughable. It's still an unknown whether or
not they are physically possible, and outside of the part of the physics
community that would like to sell you a quantum computer - or research
developing one - they're widely belived to be not physical.
Hence, these are still vague unknown weaknesses. Until progress is less vague,
actively freezing peoples' coins is not going to happen.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
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/aHuKIKqvCZl5rcEX%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-07-19 12:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 21:36 [bitcoindev] " Jameson Lopp
2025-07-13 23:19 ` [bitcoindev] " Tadge Dryja
2025-07-14 2:07 ` Antoine Riard
2025-07-14 16:08 ` Ethan Heilman
2025-07-15 2:50 ` Boris Nagaev
2025-07-14 18:52 ` Jameson Lopp
2025-07-19 12:05 ` Peter Todd [this message]
2025-07-20 15:56 ` 'conduition' via Bitcoin Development Mailing List
2025-07-20 17:39 ` Marin Ivezic
2025-07-14 13:50 ` Jameson Lopp
2025-07-15 2:32 ` [bitcoindev] " 'conduition' via Bitcoin Development Mailing List
2025-07-15 14:13 ` Boris Nagaev
2025-07-16 16:43 ` 'conduition' via Bitcoin Development Mailing List
2025-07-16 17:34 ` Boris Nagaev
2025-07-20 15:37 ` 'conduition' via Bitcoin Development Mailing List
2025-07-15 17:57 ` Ethan Heilman
2025-07-20 22:54 ` [bitcoindev] " Boris Nagaev
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=aHuKIKqvCZl5rcEX@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=antoine.riard@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=jameson.lopp@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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