From: rhavar@protonmail.com
To: Gregory Maxwell <greg@xiph.org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transaction Input/Output Sorting
Date: Wed, 24 Oct 2018 17:52:38 +0000 [thread overview]
Message-ID: <tQ_qHfmyWnGXpNVKNhuMEcHB7h1y9dJolTi0dGHi_vhRcV9bRJJXUPbvVc5QAptwruQ8cK1kxBYryhg4AzLX52uZ1Y7pgVONOVBxG25-8fU=@protonmail.com> (raw)
In-Reply-To: <CAAS2fgRY7Ra-pDNp-k4td9qUHtzh5Ah7t8ZWLnz35H_aAfGvGw@mail.gmail.com>
That's pretty easy to quantify. I wrote a quick script to grab the last few blocks, and then shuffle the inputs/outputs before testing if each transaction is bip69 or not.
The result was 42% of all transactions would accidentally be bip69 when randomized.
So clearly randomization is a lot more popular than bip69 at the moment, but I'm not sure that it matters much. As soon as you have more than a few inputs/outputs, you can tell with a high confidence if the transaction is bip69 or not.
And of course if you're clustering a wallet, you can figure out extremely easily how that wallet behaves wrt bip6.
-Ryan
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, October 24, 2018 9:12 AM, Gregory Maxwell via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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.
next prev parent reply other threads:[~2018-10-24 17:52 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
2018-10-24 17:52 ` rhavar [this message]
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='tQ_qHfmyWnGXpNVKNhuMEcHB7h1y9dJolTi0dGHi_vhRcV9bRJJXUPbvVc5QAptwruQ8cK1kxBYryhg4AzLX52uZ1Y7pgVONOVBxG25-8fU=@protonmail.com' \
--to=rhavar@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=greg@xiph.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