From: Anthony Towns <aj@erisian.com.au>
To: Peter Todd <pete@petertodd.org>
Cc: Murch <murch@murch.one>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] One Time Signatures ≠ One Message Signed
Date: Fri, 5 Jun 2026 17:54:50 +1000 [thread overview]
Message-ID: <aiKAytZNfih0ABff@erisian.com.au> (raw)
In-Reply-To: <aiFbBdvndmMhIcbW@petertodd.org>
On Thu, Jun 04, 2026 at 11:01:25AM +0000, Peter Todd wrote:
> On Thu, May 28, 2026 at 10:25:51AM -0700, Murch wrote:
> > One-time signature schemes are not well-suited for Bitcoin because they:
> > - cannot be used to participate in multi-user transaction (as another
> > participant could fail the process and force a second signature)
> > - incur lost funds or lost keys upon address reuse (as every node would need
> > to track every output script to prevent duplicates, and the recipient has no
> > say in their output script being sent to another time)
> > - are incompatible with transaction replacement (zero-conf enthusiasts
> > rejoice!)
> Note that you can design a message signing scheme where you can use a pubkey to
> sign a merkle tree of messages. In the case of a transaction, multiple
> conflicting versions of the transaction with different fee rates.
There's a balance to be had between what's considered part of the message
signing scheme versus what's part of the scripting language.
The scheme above could also be thought of as signing a single message
"spend this utxo is valid if this script's conditions are meant",
where the script is "or(fee <= 0.5, and(nSequence >= 100, fee <= 1.0),
and(nSequence >= 1000, fee <= 30.0))"
Delegating to a signed script like this is essentially the "graftroot"
concept.
Cheers,
aj
--
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/aiKAytZNfih0ABff%40erisian.com.au.
next prev parent reply other threads:[~2026-06-05 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 17:41 [bitcoindev] One Time Signatures as an Advantage? Jason Resch
2026-05-21 9:54 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2026-05-21 13:33 ` Jason Resch
2026-05-28 17:25 ` Murch
2026-06-04 11:01 ` [bitcoindev] One Time Signatures ≠ One Message Signed Peter Todd
2026-06-05 7:54 ` Anthony Towns [this message]
2026-06-08 10:04 ` Peter Todd
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=aiKAytZNfih0ABff@erisian.com.au \
--to=aj@erisian.com.au \
--cc=bitcoindev@googlegroups.com \
--cc=murch@murch.one \
--cc=pete@petertodd.org \
/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