public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@xiph.org>
To: belcher@riseup.net, Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transaction Input/Output Sorting
Date: Wed, 24 Oct 2018 16:12:39 +0000	[thread overview]
Message-ID: <CAAS2fgRY7Ra-pDNp-k4td9qUHtzh5Ah7t8ZWLnz35H_aAfGvGw@mail.gmail.com> (raw)
In-Reply-To: <62ab0a37-2969-d9fe-5849-9362154560d0@riseup.net>

On Wed, Oct 24, 2018 at 3:52 PM Chris Belcher via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Thanks for bringing our attention to this important topic.
>
> According to (https://p2sh.info/dashboard/db/bip-69-stats) around 60% of
> transaction follow bip69 (possibly just by chance).

A two input randomly ordered transaction has a 50% chance of
'following' bip-69.  So 60% sound like a small minority.


  reply	other threads:[~2018-10-24 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21 19:00 [bitcoin-dev] Transaction Input/Output Sorting rhavar
2018-10-21 21:54 ` Pavol Rusnak
2018-10-22  1:54   ` rhavar
2018-10-23 14:29     ` Chris Belcher
2018-10-24 16:12       ` Gregory Maxwell [this message]
2018-10-24 17:52         ` rhavar
2018-10-24 18:21           ` rhavar

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=CAAS2fgRY7Ra-pDNp-k4td9qUHtzh5Ah7t8ZWLnz35H_aAfGvGw@mail.gmail.com \
    --to=greg@xiph.org \
    --cc=belcher@riseup.net \
    --cc=bitcoin-dev@lists.linuxfoundation.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