From: Matt Corallo <lf-lists@mattcorallo.com>
To: Alex <alexhultman@gmail.com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Algorithm Agility for Bitcoin to maintain security in the face of quantum and classic breaks in the signature algorithms
Date: Thu, 12 Feb 2026 14:20:42 -0500 [thread overview]
Message-ID: <6485599c-e452-4efd-8375-d3b7dba36eee@mattcorallo.com> (raw)
In-Reply-To: <dd2fcc40-cedc-48ae-b23d-6029f678c184n@googlegroups.com>
On 2/12/26 10:35 AM, Alex wrote:
> > wallets aren't going to have a lot of incentive to adopt technologies that make things marginally
> more expensive.
>
> This claim is not rooted in reality. We literally just now saw Trezor market their Safe 7 as Quantum
> Ready and they had a major ad campaign specifically for this. There is major incentive for wallets
> to "sell" the quantum threat as a problem to fix, and therefore sell more wallets or claim
> compliance to gain market share. The quantum threat is mainstream. Retail knows about it, talks
> about it all the time.
>
> > many bitcoiners writing off the quantum threat
>
> Yes because psychologically, the most successful Bitcoiners are those who never reacted to any FUD
> and therefore never sold. And so they are essentially naturally selected by their history of never
> reacting to FUD. We've basically evolved the most non-reactant people and so obviously they are not
> going to react to the quantum threat because why would they change their strategy of never reacting
> if it worked so well so far?
Well you contradict yourself here :).
Yes, I fully anticipate wallets attempting to market themselves as "quantum secure". I do not
anticipate most "mainstream wallets" will care at all - if I search the app store right now for
"bitcoin wallet" I get bitcoin.com, coinbase, and trust wallet as the top three - all of which have
objective histories of taking 5-10 years to adopt incredibly basic bitcoin technologies and never
adopting best practices or marginally more complicated technologies.
And, indeed, as you point out, a large subset of the bitcoin community is unlikely to care until the
threat is imminent, at which point migration is much too late. It doesn't matter if some set of
people migrate, if a large number haven't its the same net impact.
Matt
--
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/6485599c-e452-4efd-8375-d3b7dba36eee%40mattcorallo.com.
next prev parent reply other threads:[~2026-02-13 16:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 14:20 Ethan Heilman
2026-02-10 8:53 ` Jonas Nick
2026-02-10 16:44 ` Ethan Heilman
[not found] ` <CAJowKg+WJLAJoMhyhVfkC9OSdks5jBieDWty9ce-Qju-84URFA@mail.gmail.com>
2026-02-10 23:13 ` Ethan Heilman
2026-02-11 0:19 ` Erik Aronesty
2026-02-11 2:40 ` Ethan Heilman
2026-02-11 7:25 ` Erik Aronesty
2026-02-11 16:37 ` Ethan Heilman
2026-02-17 4:13 ` 'conduition' via Bitcoin Development Mailing List
2026-02-17 7:39 ` 'conduition' via Bitcoin Development Mailing List
2026-02-19 14:35 ` Garlo Nicon
2026-02-20 1:41 ` Alex
2026-02-20 18:48 ` Erik Aronesty
2026-02-23 14:00 ` 'conduition' via Bitcoin Development Mailing List
2026-02-23 19:08 ` Erik Aronesty
2026-02-23 21:42 ` Ethan Heilman
2026-02-24 0:12 ` Alex
2026-02-25 10:43 ` Javier Mateos
2026-02-26 13:24 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2026-02-26 15:51 ` Matt Corallo
2026-02-27 15:18 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2026-02-27 19:31 ` 'conduition' via Bitcoin Development Mailing List
2026-03-01 12:24 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2026-03-01 21:28 ` Alex
2026-02-11 18:53 ` Matt Corallo
2026-02-11 22:57 ` Ethan Heilman
2026-02-12 14:55 ` Matt Corallo
2026-02-12 15:35 ` Alex
2026-02-12 19:20 ` Matt Corallo [this message]
2026-02-12 18:08 ` Ethan Heilman
2026-02-12 19:13 ` Matt Corallo
2026-02-12 20:35 ` Ethan Heilman
2026-02-12 20:43 ` Matt Corallo
2026-02-12 15:13 ` Alex
2026-02-12 19:16 ` Matt Corallo
2026-02-12 15:36 ` waxwing/ AdamISZ
2026-02-12 19:35 ` Matt Corallo
2026-02-12 19:43 ` Matt Corallo
2026-02-14 12:39 ` waxwing/ AdamISZ
2026-02-15 12:12 ` Matt Corallo
2026-02-10 21:51 ` 'Brandon Black' via Bitcoin Development Mailing List
2026-02-10 22:19 ` Ethan Heilman
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=6485599c-e452-4efd-8375-d3b7dba36eee@mattcorallo.com \
--to=lf-lists@mattcorallo.com \
--cc=alexhultman@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