From: Erik Aronesty <erik@q32.com>
To: Matt Corallo <lf-lists@mattcorallo.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Deactivating ECDSA/Schnorr
Date: Tue, 14 Apr 2026 15:39:50 -0700 [thread overview]
Message-ID: <CAJowKgKQqRx9E-CMOSJGgOWBO9ew2RxxNOMH4WAh=h3wOozEvw@mail.gmail.com> (raw)
In-Reply-To: <96E39817-8253-4AF6-86FF-E9573BC08895@mattcorallo.com>
[-- Attachment #1: Type: text/plain, Size: 3363 bytes --]
Well, I guess we have to trust that the market isn't stupid and won't
invest in spurious or forged results. I guess that's rare enough.
Crypographically negligible.
On Tue, Apr 14, 2026 at 3:29 PM Matt Corallo <lf-lists@mattcorallo.com>
wrote:
> Firstly I want to echo everything conduition said but I want to raise one
> further point.
>
> You don’t get to decide. Nor do I. The market does.
>
> Both bitcoins will, without question, exist - one where insecure spend
> paths are disabled (with the exceptions conduition raises, and probably
> any more we can come up with [1])) and one where they are not, and the
> market will decide which it prefers.
>
> I’m quite confident the market is going to pick the side that has
> something like 100x less supply, especially if it avoids burning any coins
> to the maximum extent possible…the law of supply and demand doesn’t care
> all that much about our feelings on the matter.
>
> Matt
>
>
> [1] I’ve noted before we should allow for both seedphrase recovery schemes
> as well as a commit-before-Q-day-reveal-after scheme to allow anyone who
> has keys to non-seedphrase coins to retain ownership without having to go
> to chain. This may bee important, for example, for the owner of the patoshi
> coins.
>
> On Apr 14, 2026, at 14:51, Erik Aronesty <erik@q32.com> wrote:
>
>
> 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
> <https://groups.google.com/d/msgid/bitcoindev/CAJowKgJcGTvkzjkRN3cd8LRkfazWycSp8p6oOd5D5dtEYRaB1w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>
--
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/CAJowKgKQqRx9E-CMOSJGgOWBO9ew2RxxNOMH4WAh%3Dh3wOozEvw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 6276 bytes --]
prev parent reply other threads:[~2026-04-15 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 18:37 Erik Aronesty
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 [this message]
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='CAJowKgKQqRx9E-CMOSJGgOWBO9ew2RxxNOMH4WAh=h3wOozEvw@mail.gmail.com' \
--to=erik@q32.com \
--cc=bitcoindev@googlegroups.com \
--cc=lf-lists@mattcorallo.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