From: Erik Aronesty <erik@q32.com>
To: "waxwing/ AdamISZ" <ekaggata@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: The limitations of cryptographic agility in Bitcoin
Date: Wed, 25 Feb 2026 06:39:57 -0800 [thread overview]
Message-ID: <CAJowKgJwq88yfJEQzZ+v-33EtEuYif1y6qsXtyoRyk2V+44cww@mail.gmail.com> (raw)
In-Reply-To: <823db0fa-08d3-4273-a428-04dc3d6da4d2n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
> I'm in, I think, a group of people now, that have pointed this out, here
> and elsewhere ... I like to call it the "epistemological problem" because,
> why use short words when a long one will do :) The scenario is all the
> worse because (as, again, has been pointed out before): the "I have a CRQC"
> signed message you mention is (more likely), or can be, someone who has
> just placed a short in the market, rather than an actual CRQC holder. The
> point is that during a period from "bitcoin doesn't have PQ algos" to
> "bitcoin has PQ algos" the transition will always be essentially 100%
> opaque; every honest action of moving to safety looks identical, onchain,
> to theft.
>
a key that is crackable in-advance of bitcoin being cracked, so that we
know quanutm is "real".
1. deterministic random elliptic-curve address on a much
smaller-bit-strength curve, but not so much smaller that classical attacks
are feasable
2. bounty for the solution enforceable with a smart contract
3. refusal to accept that "i have a CRQC" message unless this
well-known-key is used, because anything else is likely a scam (private key
known in advance)
4. understanding that cracking a 180-bit key only gives us 6 months to a
year of quantum engineering scaling to fix bitcoin
6. published plan to move quickly as needed
the physics is cool, but the engineering needed to scale may still well be
impossible in the physical world. bitcoin *cannot* respond to claims that
unicorns exist with protocol changes. but we *can* respond with a bip that
allows us to rapidly deploy defense against unicorn horns once irrefutable
evicence arrives that they exist.
--
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/CAJowKgJwq88yfJEQzZ%2Bv-33EtEuYif1y6qsXtyoRyk2V%2B44cww%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2708 bytes --]
next prev parent reply other threads:[~2026-02-25 15:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 16:20 [bitcoindev] " Pieter Wuille
2026-02-13 19:39 ` Erik Aronesty
2026-02-13 21:50 ` Light
2026-02-13 22:52 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2026-02-14 3:43 ` Light
2026-02-17 14:11 ` Garlo Nicon
2026-02-16 9:59 ` sadiq Ismail
2026-02-13 21:54 ` Ethan Heilman
2026-02-14 12:02 ` [bitcoindev] " waxwing/ AdamISZ
2026-02-17 3:49 ` [bitcoindev] " 'conduition' via Bitcoin Development Mailing List
2026-02-17 20:04 ` [bitcoindev] " Pieter Wuille
2026-02-19 7:22 ` 'conduition' via Bitcoin Development Mailing List
2026-02-25 12:00 ` waxwing/ AdamISZ
2026-02-25 14:39 ` Erik Aronesty [this message]
2026-02-25 22:43 ` Ethan Heilman
2026-02-26 2:07 ` Alex
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=CAJowKgJwq88yfJEQzZ+v-33EtEuYif1y6qsXtyoRyk2V+44cww@mail.gmail.com \
--to=erik@q32.com \
--cc=bitcoindev@googlegroups.com \
--cc=ekaggata@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