From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 28 Apr 2026 13:47:12 -0700 Received: from mail-qt1-f189.google.com ([209.85.160.189]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wHpKp-00015I-6E for bitcoindev@gnusha.org; Tue, 28 Apr 2026 13:47:12 -0700 Received: by mail-qt1-f189.google.com with SMTP id d75a77b69052e-50e5a336b44sf6474311cf.0 for ; Tue, 28 Apr 2026 13:47:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1777409225; x=1778014025; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=8QfxFywgjyNGq0YGPH4h1whUJTkk4yYWbTV19fTmz8w=; b=XUO6K1MbEAHocIcSBflWN7KkB1TTnNSZLQ+M5AyCG4tWXwwzrxogO4tr2Ms73kaRuQ tkXnhaGrz6xyfn4D3A3EN86eeqhEhYh6cgKiNR6RbbdtaQyuJz7vw2cGcXJhe7iBV/Lh aZYnbb6beYvlrjwJGuT5TPWrhuF/hTSO+oMoz7Jp7UPdXCYGrcwzeALl4eZVCrosqzBZ 2UqF0uyF0tkzfyaT5TXSf4vfHcV6gIlFjSoOPVtblWIiJP3JueO9mP42bQuGsGXj+sDf groRJRkENq/GJt84AslY6mRiXuFk1UJolDi3WOU2RW1IAr12lv0bYYcmZpXHL6AoWMM7 q38g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1777409225; x=1778014025; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=8QfxFywgjyNGq0YGPH4h1whUJTkk4yYWbTV19fTmz8w=; b=gZQiEW5sY3c7x8D4p1rd81RaVBT/6oek5NcH+e/dYg525j5bOa99OT+uaZJJXPar5T omUNxR4a765NzBzKwd/T44R9s6veuku63nX7dSAbjIjbShduWF2lK2b63wXxExBa+aPw Yg+BYNlV4u3YSXwD6aV4qtpuSLohrfjcBwdNdwfxVJ3Qxvek2iWpil3Y7F+ppLypRuyn gqX7MTZ25U9v3oa7vNLFiPKByNDt2LeFk13qrzCseMEPLezgHKYqd0ZtVWsD4tfZoF5O YwN7n168tFGyfZjOfPw4Dc3Ov7kJdlBxv26CCKsrBUiFNL6qM4m5fHd7jY5KPeyPG6w0 rzRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777409225; x=1778014025; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=8QfxFywgjyNGq0YGPH4h1whUJTkk4yYWbTV19fTmz8w=; b=a3K5Ffp7M9bBhVIg83dw6wf+mjLHqNWRoIbjewTy4oDGUZmBp9hBhisl61WOLfk+Be RAwvKjv9jMXPmXF7SoMKhVsmIW3/aGMHp3J6pxea9iNmaMiv0aDEvMra+Fr5cw6h4516 6AX+mCr2fJP4WEX3jhgfHMS3ARBuI3npMcAwFn6r3l3I1vxMRx8RIZeV4W0UGwk6AFAk 0n+VqHfBh7vC9rjP6KpAabkxz6A5vN/qZ844p9GBwEDpmNtoxWi0xei1Ubvc0Qhe3gvu eBXcGlZHzD7GV2s0yga9BidI8xIBdXv5eXPEwZ6ET8PXM15awk9mRIErYkTXma0MPtnn +wTg== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AFNElJ/3Qn70VllQX4XD+dSAmP9vO0CaKAW0+MGyQ9OHNGMdtxrs/Hn6P1oy9lP0GWjS44GqDmJ26P5Z1jj3@gnusha.org X-Gm-Message-State: AOJu0YzcXcEGD7xhzQ7JoujBFuz8g5fKEEY7sBhu1YvusAhBRJIxA3uW RoDAqd3aeqBWEe5MKCmY1nDJMl94kvREAmAzgyZWkB1ZFIMld3FRDqhX X-Received: by 2002:a05:622a:124a:b0:50f:c403:7ffb with SMTP id d75a77b69052e-51019e2e33emr7093501cf.18.1777409224780; Tue, 28 Apr 2026 13:47:04 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AUV6zMNHzbSsmcAsQjTfHlmfBGDMS7rag0R8bpiUz4T2qJ3UGQ==" Received: by 2002:a05:622a:205:b0:506:a3ff:ffb7 with SMTP id d75a77b69052e-50e3de304c3ls159674961cf.0.-pod-prod-03-us; Tue, 28 Apr 2026 13:46:57 -0700 (PDT) X-Received: by 2002:a05:620a:258d:b0:8f2:4470:4796 with SMTP id af79cd13be357-8f7d783482fmr601950985a.20.1777409217489; Tue, 28 Apr 2026 13:46:57 -0700 (PDT) Received: by 2002:a05:690c:23c8:b0:7ba:f1b3:9504 with SMTP id 00721157ae682-7baf1b3bccams7b3; Thu, 23 Apr 2026 01:46:25 -0700 (PDT) X-Received: by 2002:a05:690c:e3cb:b0:7b2:9347:7be1 with SMTP id 00721157ae682-7b9ecf86543mr271965187b3.29.1776933984602; Thu, 23 Apr 2026 01:46:24 -0700 (PDT) Date: Thu, 23 Apr 2026 01:46:24 -0700 (PDT) From: Louise Michel To: Bitcoin Development Mailing List Message-Id: In-Reply-To: References: Subject: [bitcoindev] Re: Deactivating ECDSA/Schnorr MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_446118_1967439998.1776933984130" X-Original-Sender: barsonneck@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_446118_1967439998.1776933984130 Content-Type: multipart/alternative; boundary="----=_Part_446119_1677306834.1776933984130" ------=_Part_446119_1677306834.1776933984130 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Erik - You were right to balk at some of the ideas that have been brought into the= =20 milieu around Bitcoin. There is no acceptable number of UTXOs to confiscate= =20 or lock out in Bitcoin. Outputs should continue to function unimpeded in=20 the way they did when they were first inscribed in the blockchain. It is=20 the prerogative of the users to decide if, when, how, and for what reason= =20 they move and safeguard their value, not just because it is their property.= =20 And it is a good idea for users to be informed and educate themselves about= =20 the features and risks of the various tools and output types that allow=20 them to do so. Certainly, new alternatives are worth exploring, but no options are without= =20 tradeoffs. Bitcoin users should think carefully about what these are and=20 should evaluate for themselves the alternatives and their own threat=20 models. Ironically, the lesson of the DAO Hack might as well be that clever= =20 -- but ultimately misguided and mis-implemented -- mechanisms have the=20 potential to cripple a cryptocurrency. Of course, some users have lost access to their keys, or may simply refuse= =20 to move their bitcoin, and some powerful cryptanalysts from the future may= =20 one day recover keys and steal value (or maybe they won't). Developing=20 options for such a future is clearly a high priority for a subset of=20 Bitcoin users, but forks have to be carefully regarded because they are=20 highly consequential. Unlike Ethereum, Bitcoin is an immutable chain. In Bitcoin, history doesn't= =20 get re-written and consensus valid transactions that pay a market fee can= =20 be included in a future block. Opting others into schemes they did not=20 consent to ex post facto is misguided at best. There may come a day when it= =20 no longer makes sense to create new, legacy output types, and we have seen= =20 that the market could just as well handle this. Virtually no one creates=20 P2PK outputs today. Still, no threat justifies retroactively restricting,= =20 disabling, or stealing the property and value of others. As M. Corallo points out, the market will ultimately decide.=20 Louise On Tuesday, April 14, 2026 at 12:51:06=E2=80=AFPM UTC-6 Erik Aronesty wrote= : > Deactivating ECDSA/Schnorr based schemes should not be discussed=20 > seriously. =20 > > You give people alternatives, yes. I'm a big fan of quantum optionality.= =20 > > But we cannot have a forced vaccination situation.=20 > > > There is simply no credible way you can convince somebody who is sovereig= n=20 > that their encryption algorithm is broken aside from breaking it.=20 > > People can send to bad keys today. > > There are lots of op codes that let people shoot themselves in the foot= =20 > > Bitcoin is not a nanny state. > > "oh no someone might break satoshi's keys"=20 > > Let them. if satoshi's 50 Bitcoin stash keys serve to be the bounty that= =20 > propels humanity to a future of limitless unbounded magical computing tha= t=20 > is not a problem we need to solve right now.=20 > > The worst possible thing we could do is confiscate everybody's coin and= =20 > move to a NISD approved algorithm on the say so of large government funde= d=20 > organizations. > > That sounds dystopian at best.=20 > > > > > > > > --=20 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 e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= b6a90e69-513b-4f6f-91dd-1de8a4d9d1edn%40googlegroups.com. ------=_Part_446119_1677306834.1776933984130 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Erik -

You were right to balk at some of th= e ideas that have been brought into the milieu around Bitcoin. There is no = acceptable number of UTXOs to confiscate or lock out in Bitcoin. Outputs sh= ould continue to function unimpeded in the way they did when they were firs= t inscribed in the blockchain. It is the prerogative of the users to decide= if, when, how, and for what reason they move and safeguard their value, no= t just because it is their property. And it is a good idea for users to be = informed and educate themselves about the features and risks of the various= tools and output types that allow them to do so.

Certainly, new alternatives are worth exploring, but no options are witho= ut tradeoffs. Bitcoin users should think carefully about what these are and= should evaluate for themselves the alternatives and their own threat model= s. Ironically, the lesson of the DAO Hack might as well be that clever -- b= ut ultimately misguided and mis-implemented -- mechanisms have the potentia= l to cripple a cryptocurrency.

Of course, some users have lost a= ccess to their keys, or may simply=20 refuse to move their bitcoin, and some powerful cryptanalysts from the future may one day recover keys and steal value (or maybe=20 they won't). Developing options for such a future is clearly a high priorit= y for a subset of Bitcoin users, but forks have to be carefully regarded be= cause they are highly consequential.

Unlike Ethe= reum, Bitcoin is an immutable chain. In Bitcoin, history doesn't get re-wri= tten and consensus valid transactions that pay a market fee can be included= in a future=20 block. Opting others into schemes they did not consent to ex post facto is = misguided=20 at best. There may come a day when it no longer makes sense to create new, = legacy output types, and we have seen that the market could just as well ha= ndle this. Virtually no one creates=20 P2PK outputs today. Still, no threat justifies retroactively restricting, d= isabling, or stealing the property and value of others.

As M. Corallo points out, the market will ultimately decide.=C2=A0<= /div>

Louise
On Tuesday, April 14, 2026 at 12:51:06=E2=80= =AFPM UTC-6 Erik Aronesty wrote:
Deactivating ECDSA/= Schnorr based schemes should not be discussed seriously.=C2=A0=C2=A0
<= div dir=3D"auto">
You give people alternatives, = yes. I'm a big fan of quantum optionality.=C2=A0

But we cannot have a forced vaccination situat= ion.=C2=A0


There is simply no credible way you can convince somebody wh= o is sovereign that their encryption algorithm is broken aside from breakin= g it.=C2=A0

People can s= end to bad keys today.

T= here are lots of op codes that let people shoot themselves in the foot=C2= =A0

Bitcoin is not a nan= ny state.

"oh no so= meone might break satoshi's keys"=C2=A0
Let them.=C2=A0 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 no= w.=C2=A0

The worst possi= ble 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 a= t best.=C2=A0


=


<= br>


--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/b6a90e69-513b-4f6f-91dd-1de8a4d9d1edn%40googlegroups.com.
------=_Part_446119_1677306834.1776933984130-- ------=_Part_446118_1967439998.1776933984130--