From: Peter Todd <pete@petertodd•org>
To: Russell O'Connor <roconnor@blockstream•com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Standard Unstructured Annex
Date: Tue, 29 Apr 2025 02:59:07 +0000 [thread overview]
Message-ID: <aBBAe265_h9A_lNz@petertodd.org> (raw)
In-Reply-To: <CAMZUoKmu8NeFzjU1vuU6AmxZ0T7VnZ-s7rqsHaiZjmZrL3v5DQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
On Mon, Apr 28, 2025 at 12:25:08PM -0400, Russell O'Connor wrote:
> Ah nevermind, I get it now.
>
> The contrapositive of this proposed standardness rule is that if one annex
> is empty, then all annexes must be empty. Therefore if on participants
> signs an empty annex, then standardness would imply that all the annexes
> must be empty.
You're almost correct.
There is a consensus distinction between having an annex, and not having
an annex at all. That means a zero-byte annex is different from not
having an annex at all.
So with my proposed rule, inputs can either have no annex at all (the
standard status quo), or an annex of zero or more bytes.
If any input has an annex, *all* inputs must have an annex. However, for
efficiency, they're allowed to have a completely empty, zero-byte,
annex. So basically an empty annex is just the defined way for an input
to sign their approval of the use of annexes in that transaction (and
subsequent tx pinning risk).
--
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/aBBAe265_h9A_lNz%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-04-29 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 0:27 Peter Todd
2025-03-20 22:47 ` [bitcoindev] " Antoine Riard
2025-03-24 16:17 ` Peter Todd
2025-04-09 22:55 ` Antoine Riard
2025-04-28 16:13 ` [bitcoindev] " 'Russell O'Connor' via Bitcoin Development Mailing List
2025-04-28 16:25 ` 'Russell O'Connor' via Bitcoin Development Mailing List
2025-04-29 2:59 ` Peter Todd [this message]
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=aBBAe265_h9A_lNz@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=roconnor@blockstream$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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