Delivery-date: Wed, 04 Jun 2025 00:57:00 -0700 Received: from mail-yb1-f189.google.com ([209.85.219.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 1uMizb-0004Xz-1D for bitcoindev@gnusha.org; Wed, 04 Jun 2025 00:56:59 -0700 Received: by mail-yb1-f189.google.com with SMTP id 3f1490d57ef6-e7dd83f8690sf9262204276.2 for ; Wed, 04 Jun 2025 00:56:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1749023813; x=1749628613; 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=zlPRDg/6shO5+15ItbV6l/OnXqgaAiyxL5wNLgfQ0L8=; b=J87lYbcBZMbvroU2xOJsL3KvuOrHoUIrChBslOlAuUDS7D0K1iXiyFN0t8YfB4JTfV KXiSECSuCmiNAJdLIMic4AXYx3QZx4z1vL+ntY5PXs/BVkN9jcx46wtJJ03+agAa8Hz0 FEVZZVdDTmjy5aKdLQ+SOKISfIvcezs3/aN+AHPZ6jhHVpRI+x23dNeM0o8m1dtWKDwf Pjk9tPTKsvS48LzBWo+Qmo5JUVsmWZUhS4ffD2JbsDaTKxta8Q6E9Wstmis23oVtTeM+ Hcr0CUNzmBXNiW9FAokXbSrH7U2TfRuw0rnA/aWSwUcE3TDIgD3goarCRzibD3Y67P5a p5Dg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749023813; x=1749628613; 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=zlPRDg/6shO5+15ItbV6l/OnXqgaAiyxL5wNLgfQ0L8=; b=bh4axTOgU5/c82dbDcZeqTo3XzF/DyhFXQ1wMG+prQ+l9XYgxCQlIL4/hS+iN7x+N0 0HRJThYl3jqWlvSkwpLL+IM4S4Idew0O7jGDekffwhfGURYmEXXVj7/9+fYgB/d2IdhW nJIYLPf66GYNqRuhGd70hGfYlOtXD+vxnwm5sLwPAphQqMMKvuqmyXe9WiHHB7i9JLjz RURWUA1z4+FX+eL8WPaZowz+/59al9TWK/AoIgHHzXjyGjzbJ3sQhmX/2eWbszUtC++l i8Bwq834/9p1mKCR9DMygAB9aAh1lBeHoQxiIHunvZ4v1/hA/xJD1tqrvfvcnDOgV2TZ B8Bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749023813; x=1749628613; 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=zlPRDg/6shO5+15ItbV6l/OnXqgaAiyxL5wNLgfQ0L8=; b=uDyXRNVBKtE+XFqoAeugqbexpFf/WSl+fZnrfg+mmgR1WisNg1ROF9rLyFwKPo+V6L jQHpsFwkZL5WebJd/QUalno6n6+Yi6535inT906T39h5SfKiyfvbAKBwuRck65QCknPP 9ywxB0HPu0bvyTtXTgmktZGKK7hdCEyUV6Gcmp9CiJ7FfPPXBEGt6mSRHJcZNN+7Yzus QBWma5l1UvI81bqI7GrT5rTzWEzoyTHBpH/KfrLauIkwf/iNJ3Uhkstxg4A1rBRrqYIx zM9s+mGIZdXPHzj4yFGo1LcBOV9e95UDso0iJSuTRDqXmSZ9BnOq5XWTLmPoX7tqm1/A wCrA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCXYLpPK5k4rM3xSIxsk1KbphgQ4EySnejyDLkZj4pTvKxOU6x0ZzAfyaIQhAjsfC0ggVQTYP/dW9nG5@gnusha.org X-Gm-Message-State: AOJu0YwwqyraaemxDmf7JHT4wGuQHTuC8e4IifogYNf4/O/aQr9ah5s4 m8r3mO5gDIKdf5ZQN4/4K3YiMvH2o3Sy40g8p6vWdbS8naC0EBlaJ6xc X-Google-Smtp-Source: AGHT+IEqnhIIXAlw0kkbrubW6YYPPgvMot4wyb10fNXnXBiEmIdTh9+Ha/5/JTZPtDlqDj4cKe2EXg== X-Received: by 2002:a05:6902:1a4a:b0:e7e:fa65:8fec with SMTP id 3f1490d57ef6-e8179dad833mr2031045276.41.1749023812815; Wed, 04 Jun 2025 00:56:52 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZdt/OjtOACoY2wW8SznvA7boydTH/nAGo19LxuaQnUoWA== Received: by 2002:a25:b216:0:b0:e7d:cffc:6cc with SMTP id 3f1490d57ef6-e7f6f7f5cb8ls7010356276.2.-pod-prod-06-us; Wed, 04 Jun 2025 00:56:49 -0700 (PDT) X-Received: by 2002:a05:690c:45c6:b0:70e:86a:ae12 with SMTP id 00721157ae682-710d9d6e3ddmr21277497b3.8.1749023809137; Wed, 04 Jun 2025 00:56:49 -0700 (PDT) Received: by 2002:a05:690c:6083:b0:70e:2cf8:9db8 with SMTP id 00721157ae682-70f980e43fams7b3; Mon, 2 Jun 2025 11:54:09 -0700 (PDT) X-Received: by 2002:a05:690c:6d12:b0:70e:23e6:60f7 with SMTP id 00721157ae682-71057d20cf9mr196974207b3.27.1748890448724; Mon, 02 Jun 2025 11:54:08 -0700 (PDT) Date: Mon, 2 Jun 2025 11:54:08 -0700 (PDT) From: Jonathan Voss To: Bitcoin Development Mailing List Message-Id: <16f0f405-3f39-498e-9399-a6050773c4c7n@googlegroups.com> In-Reply-To: References: Subject: Re: [bitcoindev] Post-Quantum commit / reveal Fawkescoin variant as a soft fork MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_190950_1585333022.1748890448370" X-Original-Sender: K98kurz@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_190950_1585333022.1748890448370 Content-Type: multipart/alternative; boundary="----=_Part_190951_868540719.1748890448370" ------=_Part_190951_868540719.1748890448370 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If using a monetary network requires out-of-band payments, then that=20 severely limits the actual utility of the monetary network as a medium of= =20 exchange. Imagine if the only way to make a bank transfer was to first go= =20 in-person to the bank of the recipient of the transfer to give them=20 something that then allowed your bank to make the transfer -- it would be= =20 an unworkable monetary system. Similarly, if future Bitcoin transactions=20 require making out-of-band payments, then it has failed as a monetary=20 network with an endogenous unit of account. The whole system has to work=20 without reliance upon exogenous monetary media or mechanisms. As such, the= =20 commit-and-reveal scheme fails to maintain the monetary properties of the= =20 network as a whole unless we assert reliance upon altruism to get the=20 commitments into the blockchain, which instead breaks the incentive-based= =20 game theoretic design. Maybe it would work as a stop-gap solution in the=20 event of the advent of a relevant quantum computer, but it is certainly not= =20 a good long-term plan as currently formulated. Recall the original premise: "Bitcoin: A Peer-to-Peer Electronic Cash=20 System". If you can't transact with it as cash, i.e. as the ultimate=20 endogenous settlement mechanism, then it is no longer Bitcoin. Requiring an= =20 exogenous system fundamentally breaks the model. -- Jonathan On Monday, June 2, 2025 at 9:53:55=E2=80=AFAM UTC-4 Peter Todd wrote: > On Fri, May 30, 2025 at 03:00:41PM -0700, Jonathan Voss wrote: > > As far as I can tell, the main flaw in commit/reveal protocols is in th= e=20 > > commit phase: if revealing a commitment with N confirmations is require= d=20 > to=20 > > spend bitcoins, then, without spending any bitcoins, how do you get the= =20 > > commitment into the blockchain in the first place? Maybe I am just=20 > > misunderstanding this. If so, then a commit/reveal scheme may be a=20 > workable=20 > > solution. > > You can always purchase new BTC to perform the commitment. > > Indeed, this problem is often seen in alt-coins where fees must be paid i= n=20 > a > native asset, while users are trying to send some kind of tokenized asset= =20 > like > a USD token. You can have funds that you can't move because you don't hav= e=20 > the > correct asset. While annoying, this isn't a fatal problem. > > --=20 > https://petertodd.org 'peter'[:-1]@petertodd.org > --=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/= 16f0f405-3f39-498e-9399-a6050773c4c7n%40googlegroups.com. ------=_Part_190951_868540719.1748890448370 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If using a monetary network requires out-of-band payments, then that severe= ly limits the actual utility of the monetary network as a medium of exchang= e. Imagine if the only way to make a bank transfer was to first go in-perso= n to the bank of the recipient of the transfer to give them something that = then allowed your bank to make the transfer -- it would be an unworkable mo= netary system. Similarly, if future Bitcoin transactions require making out= -of-band payments, then it has failed as a monetary network with an endogen= ous unit of account. The whole system has to work without reliance upon exo= genous monetary media or mechanisms. As such, the commit-and-reveal scheme = fails to maintain the monetary properties of the network as a whole unless = we assert reliance upon altruism to get the commitments into the blockchain= , which instead breaks the incentive-based game theoretic design. Maybe it = would work as a stop-gap solution in the event of the advent of a relevant = quantum computer, but it is certainly not a good long-term plan as currentl= y formulated.

Recall the original premise: "Bitcoin: A= Peer-to-Peer Electronic Cash System". If you can't transact with it as cas= h, i.e. as the ultimate endogenous settlement mechanism, then it is no long= er Bitcoin. Requiring an exogenous system fundamentally breaks the model.

-- Jonathan

On Monday, June 2, 2025= at 9:53:55=E2=80=AFAM UTC-4 Peter Todd wrote:
On Fri, May 30, 2025 at 03:00:41PM -0700= , Jonathan Voss wrote:
> As far as I can tell, the main flaw in commit/reveal protocols is = in the=20
> commit phase: if revealing a commitment with N confirmations is re= quired to=20
> spend bitcoins, then, without spending any bitcoins, how do you ge= t the=20
> commitment into the blockchain in the first place? Maybe I am just= =20
> misunderstanding this. If so, then a commit/reveal scheme may be a= workable=20
> solution.

You can always purchase new BTC to perform the commitment.

Indeed, this problem is often seen in alt-coins where fees must be paid= in a
native asset, while users are trying to send some kind of tokenized ass= et like
a USD token. You can have funds that you can't move because you don= 't have the
correct asset. While annoying, this isn't a fatal problem.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--
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/16f0f405-3f39-498e-9399-a6050773c4c7n%40googlegroups.com.
------=_Part_190951_868540719.1748890448370-- ------=_Part_190950_1585333022.1748890448370--