Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id CC6D6105D for ; 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 ; 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 , Bitcoin Protocol Discussion From: rhavar@protonmail.com Reply-To: rhavar@protonmail.com Message-ID: In-Reply-To: References: <62ab0a37-2969-d9fe-5849-9362154560d0@riseup.net> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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.