From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 02 Jun 2025 09:02:08 -0700 Received: from mail-yw1-f192.google.com ([209.85.128.192]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1uM7bz-0006CS-PO for bitcoindev@gnusha.org; Mon, 02 Jun 2025 09:02:08 -0700 Received: by mail-yw1-f192.google.com with SMTP id 00721157ae682-70e5ae5c517sf61681367b3.1 for ; Mon, 02 Jun 2025 09:02:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1748880122; x=1749484922; 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=ExC1ALPlCifDjqh1T530ucXXjBUxPttiwSkeYLopDqo=; b=twjYr8lCv39odvlvf6DjrkZYWXIGVi5BCpvF6nvlMKI67Os6R6EBcfKS/+Cf0zdwCv MtrCTGYWzI4uvuxAzCpWKpfbN73m92oTKHqKjAjoTpJBDIuYyBGUJDxlpoAyjoSaXq0o K7ShYp0mz2JEcREzzI7uz/npHVAxvBmQiDDNnVunHXoMD2BlGd7eIQyaToPm7cw0uY/S fI/ZFb0tfM1wkfloCn7pS1bPRYxgOUaBc0of5ncR9XxLZB/PNjO+v5yiW3mm889J1i5r wEBuI0tFErgiYmsS7xDhLwlP8w6/UbH6Zl9yf8RTK8RvDyIS6c1kaajl0n0T5kl9AuYw 2aGA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1748880122; x=1749484922; 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=ExC1ALPlCifDjqh1T530ucXXjBUxPttiwSkeYLopDqo=; b=ToIDapBc1UNWA4A9mqQMSCvXIWEJf4nIKT4KU+588DMf2peM0C+NsjJke7kzHhmiPp qlE7JaCu43Ruho82PgBuWeL4K5c4CnTC/aa6jWOXUBQ78D1gnm5vZ++pvGyBjWqmKIRW io9LWzYPF1Nn8Y+b6OqR4D5G7DcVFhPMS/vWSN/Jw/yGDBBRaWKeHu6vw8HJw93FzQaK s4uE5/157ZnwhD58RwyFFFXDYqAtE+DY0KRcBCxy+ej4GibcDAkvoy40ewzA1P3YJKb+ ABmdmni/q+xqKDkV78FtO0nJhFt9gIZa6eNalMbU2BRZkPwffFJ5Nx6i52YZNyTR+d0E jpmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1748880122; x=1749484922; 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=ExC1ALPlCifDjqh1T530ucXXjBUxPttiwSkeYLopDqo=; b=fCa/DIZ1Q2rDPodsp6/sJ7AsdpYe826NqdiE79xjuYV47FLoYzb5z2eW72zVMd3OJ9 bBfKqG9zLzzI/De/rnVTC97G7UGxRvl4WOqXF9Ec/GMlKp0rHSwG3Tzfb5Zej5yzE8B4 8RUIId9yK3cs4XsUGKYTX3CCMhgko1FuvUfnKitMjX0SzfO7RIF7DGUpu6LRP5MmcZ7H PFBIGBVAzTwyJ/rVEOp5/NiLJ1l4rBrh+RZQuHJ7E4uBoY6++uwrPsrEQsaVZcLj2V9t eRIgzzbphNMS3yI25DYBGLSdBz33X9fyPRJW7WK7oxWn9rriNEJKuyR7oo5tyvYFnLcK 99zQ== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWLZTrWXaL66S7BGIeDAArwCcCN6UT9ix4ailktHrFam5kPbme31eDcO0vwZOrZP4j++cNZVH0+1POJ@gnusha.org X-Gm-Message-State: AOJu0YyxMnOEOUSFj4BaYtToQlUnmDPrtbqHkH/giQG2c6Z786+iKWTF vV0xvr50tthGTuR1qDccrkBwv8wPTjo42U9/0z2EYSpekIylszn8bX22 X-Google-Smtp-Source: AGHT+IHSC5si5qUgppKVr5YtNGi1/HOsNgHcdfA1QeZf8akZt8oxBqN3NdzQ4M2LVbphDdgwxiZflQ== X-Received: by 2002:a05:6902:2013:b0:e7d:b5bc:aa81 with SMTP id 3f1490d57ef6-e8128dc86c5mr10371040276.27.1748880121817; Mon, 02 Jun 2025 09:02:01 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZf1NEj/ygpPivImlPXL80tKQ+x5QGjRKgSuto1sv45yOg== Received: by 2002:a25:dc91:0:b0:e7d:7490:4a2b with SMTP id 3f1490d57ef6-e7f6f7d969fls4998804276.1.-pod-prod-02-us; Mon, 02 Jun 2025 09:01:56 -0700 (PDT) X-Received: by 2002:a05:690c:6705:b0:70e:195:e924 with SMTP id 00721157ae682-70f97f3212fmr177897517b3.36.1748880116700; Mon, 02 Jun 2025 09:01:56 -0700 (PDT) Received: by 2002:a05:690c:6083:b0:70e:2cf8:9db8 with SMTP id 00721157ae682-70f980e43fams7b3; Mon, 2 Jun 2025 08:50:30 -0700 (PDT) X-Received: by 2002:a05:690c:6f06:b0:6f9:7920:e813 with SMTP id 00721157ae682-70f97e2e318mr191520667b3.4.1748879428894; Mon, 02 Jun 2025 08:50:28 -0700 (PDT) Date: Mon, 2 Jun 2025 08:50:28 -0700 (PDT) From: Q C To: Bitcoin Development Mailing List Message-Id: <77c90109-6f21-4f92-b122-0a7034fb1a87n@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_322516_1630944952.1748879428552" X-Original-Sender: dogeprotocol1@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_322516_1630944952.1748879428552 Content-Type: multipart/alternative; boundary="----=_Part_322517_897132115.1748879428552" ------=_Part_322517_897132115.1748879428552 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable *>>> You can always purchase new BTC to perform the commitment.*Jonathan's= =20 was probably referring to the public-key being exposed when performing the= =20 commitment (since this would defeat the purpose). >From first post from Tadge in this thread, the payment needs to be made out= =20 of band, so the public key isn't exposed during the commitment phase: >>> get that txid into an OP_RETURN output somehow (paying a miner out of= =20 band, etc) On Monday, June 2, 2025 at 6:53:55=E2=80=AFAM UTC-7 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/= 77c90109-6f21-4f92-b122-0a7034fb1a87n%40googlegroups.com. ------=_Part_322517_897132115.1748879428552 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
>>> You can always purchase new BTC to perform the commitment.

J= onathan's was probably referring to the public-key being exposed when perfo= rming the commitment (since this would defeat the purpose).

From= first post from Tadge in this thread, the payment needs to be made out of = band, so the public key isn't exposed during the commitment phase:
>>> get that txid into an OP_RETURN output somehow (paying a miner out of band,= etc)


On Monday, June 2, 2025 at 6:53:55=E2=80=AFAM UTC-7 Pet= er Todd wrote:
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/77c90109-6f21-4f92-b122-0a7034fb1a87n%40googlegroups.com.
------=_Part_322517_897132115.1748879428552-- ------=_Part_322516_1630944952.1748879428552--