From: Peter Todd <pete@petertodd.org>
To: Jonathan Voss <k98kurz@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Post-Quantum commit / reveal Fawkescoin variant as a soft fork
Date: Mon, 2 Jun 2025 11:24:36 +0000 [thread overview]
Message-ID: <aD2J9HNJUqaod0n2@petertodd.org> (raw)
In-Reply-To: <c8bbcbbb-036b-4e72-9bb5-4490e43dda21n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
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
> commit phase: if revealing a commitment with N confirmations is required to
> spend bitcoins, then, without spending any bitcoins, how do you get the
> commitment into the blockchain in the first place? Maybe I am just
> misunderstanding this. If so, then a commit/reveal scheme may be a workable
> 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 asset 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.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
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/aD2J9HNJUqaod0n2%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-06-02 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 17:14 [bitcoindev] Post-Quantum commit / reveal Fawkescoin variant as a soft fork Tadge Dryja
2025-05-28 18:20 ` Sergio Demian Lerner
2025-05-28 20:24 ` Nagaev Boris
2025-05-30 22:00 ` Jonathan Voss
2025-06-02 11:24 ` Peter Todd [this message]
2025-06-02 15:50 ` Q C
2025-06-02 18:54 ` Jonathan Voss
2025-06-05 14:33 ` 'conduition' via Bitcoin Development Mailing List
2025-06-02 17:38 ` waxwing/ AdamISZ
2025-06-02 19:34 ` 'conduition' via Bitcoin Development Mailing List
2025-06-02 22:50 ` Nagaev Boris
2025-05-31 16:07 ` [bitcoindev] " waxwing/ AdamISZ
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=aD2J9HNJUqaod0n2@petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoindev@googlegroups.com \
--cc=k98kurz@gmail.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