summaryrefslogtreecommitdiff
path: root/08/7f73aa95fe8e746ab411c25a8029ffc4f6f653
blob: 2a045acb90d46a1f05f6481214fd71487744ef26 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
Return-Path: <rhavar@protonmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id CC6D6105D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Oct 2018 17:52:42 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1C631713
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Oct 2018 17:52:41 +0000 (UTC)
Date: Wed, 24 Oct 2018 17:52:38 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
	s=default; t=1540403559;
	bh=sftCa5V4KG7zccUB0poN5+O73st4dNLgNsSEAqWDv0E=;
	h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:
	Feedback-ID:From;
	b=Ql+huMssuGWdlx0XU27mulR93SJ1SiF3f9TzjR3scdb1nmGIuh1pd6zm6j0pObmrD
	YzTD4EOq6VANWI0WCoWWH86PC7e9v29ai8xoeUKu5cD9U14CUN1UzFFWCNUMQ2O4Im
	8YuMXNMD13yCI0Zy1neSHWv5yE3fwP24xmJ4G3pY=
To: Gregory Maxwell <greg@xiph.org>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: rhavar@protonmail.com
Reply-To: rhavar@protonmail.com
Message-ID: <tQ_qHfmyWnGXpNVKNhuMEcHB7h1y9dJolTi0dGHi_vhRcV9bRJJXUPbvVc5QAptwruQ8cK1kxBYryhg4AzLX52uZ1Y7pgVONOVBxG25-8fU=@protonmail.com>
In-Reply-To: <CAAS2fgRY7Ra-pDNp-k4td9qUHtzh5Ah7t8ZWLnz35H_aAfGvGw@mail.gmail.com>
References: <sKbqoBddMV_gqKR8AIje8pbaF9FMc0gy636OOtI5jqszGH6lRrLtDtd_bQBB_d01vexaI17N4k_Zss8aeDOOsE51VDeQ7RGC2cxv1nnc--0=@protonmail.com>
	<CAF90Avnbxd3HA0yPcr929sf0o7ihF3SgcnCfqbvAeA8uxZa4Og@mail.gmail.com>
	<oTVax1iu2AHkNx8jQ9QlnWr2FS6Uusm1zKPZOkn1XRBv5my23NvVab0lWWH3DSbt3pXEv-ZsmhhU79MGuwnUdP2EKMk931XRyvuLxPRMyjk=@protonmail.com>
	<62ab0a37-2969-d9fe-5849-9362154560d0@riseup.net>
	<CAAS2fgRY7Ra-pDNp-k4td9qUHtzh5Ah7t8ZWLnz35H_aAfGvGw@mail.gmail.com>
Feedback-ID: RdfuD--Ffc-FNb_4UIG1XA3s5stj1f6Yt84KENdha_3WoiW3STYpu7X5uGR72LvTfQZpxEhSRHGSlNfV5XM5RA==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 24 Oct 2018 19:19:09 +0000
Subject: Re: [bitcoin-dev] Transaction Input/Output Sorting
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2018 17:52:42 -0000

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 transac=
tion is bip69 or not.

The result was 42% of all transactions would accidentally be bip69 when ran=
domized.

So clearly randomization is a lot more popular than bip69 at the moment, bu=
t I'm not sure that it matters much. As soon as you have more than a few in=
puts/outputs, you can tell with a high confidence if the transaction is bip=
69 or not.

And of course if you're clustering a wallet, you can figure out extremely e=
asily how that wallet behaves wrt bip6.


-Ryan

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Wednesday, October 24, 2018 9:12 AM, Gregory Maxwell via bitcoin-dev <bi=
tcoin-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% o=
f
> > 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.