From: Erik Aronesty <erik@q32.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Deactivating ECDSA/Schnorr
Date: Tue, 14 Apr 2026 11:37:30 -0700 [thread overview]
Message-ID: <CAJowKgJcGTvkzjkRN3cd8LRkfazWycSp8p6oOd5D5dtEYRaB1w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Deactivating ECDSA/Schnorr based schemes should not be discussed
seriously.
You give people alternatives, yes. I'm a big fan of quantum optionality.
But we cannot have a forced vaccination situation.
There is simply no credible way you can convince somebody who is sovereign
that their encryption algorithm is broken aside from breaking it.
People can send to bad keys today.
There are lots of op codes that let people shoot themselves in the foot
Bitcoin is not a nanny state.
"oh no someone might break satoshi's keys"
Let them. if satoshi's 50 Bitcoin stash keys serve to be the bounty that
propels humanity to a future of limitless unbounded magical computing that
is not a problem we need to solve right now.
The worst possible thing we could do is confiscate everybody's coin and
move to a NISD approved algorithm on the say so of large government funded
organizations.
That sounds dystopian at best.
--
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/CAJowKgJcGTvkzjkRN3cd8LRkfazWycSp8p6oOd5D5dtEYRaB1w%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2340 bytes --]
next reply other threads:[~2026-04-14 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 18:37 Erik Aronesty [this message]
2026-04-14 20:25 ` 'conduition' via Bitcoin Development Mailing List
2026-04-14 21:59 ` Erik Aronesty
2026-04-15 4:27 ` Alex
2026-04-15 9:37 ` Erik Aronesty
2026-04-14 22:29 ` Matt Corallo
2026-04-14 22:39 ` Erik Aronesty
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=CAJowKgJcGTvkzjkRN3cd8LRkfazWycSp8p6oOd5D5dtEYRaB1w@mail.gmail.com \
--to=erik@q32.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