public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Greg Sanders <gsanders87@gmail•com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Ephemeral Anchors: Fixing V3 Package RBF againstpackage limit pinning
Date: Thu, 2 Feb 2023 09:52:09 -0500	[thread overview]
Message-ID: <Y9vOGVMJx1b9CPYq@petertodd.org> (raw)
In-Reply-To: <CAB3F3DvToF_fia+X5SQi-L=BDYGLpzr8nNHqjtFBUjLMbyPE9Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]

On Fri, Jan 27, 2023 at 09:05:20AM -0500, Greg Sanders via bitcoin-dev wrote:
> Hello again dev,
> 
> Due to the interest in the proposal and the prodding of certain folks, I've
> written up a short draft BIP of the Ephemeral Anchors idea here:
> https://github.com/instagibbs/bips/blob/ephemeral_anchor/bip-ephemeralanchors.mediawiki
> 
> The pull request at https://github.com/bitcoin/bitcoin/pull/26403 has been
> refreshed on top of the latest V3 proposal, but the BIP itself is
> unaffected.

The BIP states that:

    Why OP_2 not OP_TRUE? OP_TRUE is often used in test vectors, using OP_2 has
    the same benefits and none of these common collisions.

Why is a "collision" harmful in this case?

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-02 14:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 13:52 [bitcoin-dev] Ephemeral Anchors: Fixing V3 Package RBF against package " Greg Sanders
2022-10-18 15:33 ` [bitcoin-dev] Ephemeral Anchors: Fixing V3 Package RBF againstpackage " Arik Sosman
2022-10-18 15:51   ` Greg Sanders
2022-10-18 16:41     ` Jeremy Rubin
2022-10-18 18:18       ` Greg Sanders
2022-10-19 15:11       ` James O'Beirne
2022-10-20 13:42         ` Greg Sanders
2022-10-27  9:37           ` Johan Torås Halseth
2022-11-30 15:32           ` Greg Sanders
2023-01-27 14:05             ` Greg Sanders
2023-02-02 14:52               ` Peter Todd [this message]
2023-02-02 14:59                 ` Greg Sanders
2023-02-02 15:06                   ` Peter Todd
2023-02-02 18:36                     ` Greg Sanders
2023-02-02 20:22                       ` Peter Todd
2023-02-02 20:47                         ` Greg Sanders
2023-02-03 22:10                           ` Peter Todd
2023-02-04  2:07                             ` Greg Sanders
2023-02-04 16:02                               ` Peter Todd
2023-03-13 16:38                                 ` Greg Sanders
2022-10-19  0:33 ` [bitcoin-dev] Ephemeral Anchors: Fixing V3 Package RBF against package " Antoine Riard
2022-10-19 13:22   ` Greg Sanders

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=Y9vOGVMJx1b9CPYq@petertodd.org \
    --to=pete@petertodd$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=gsanders87@gmail$(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