Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z11ii-0002RK-5f for bitcoin-development@lists.sourceforge.net; Sat, 06 Jun 2015 00:12:16 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.45 as permitted sender) client-ip=209.85.215.45; envelope-from=kristovatlas.lists@gmail.com; helo=mail-la0-f45.google.com; Received: from mail-la0-f45.google.com ([209.85.215.45]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z11ig-0007O1-Ty for bitcoin-development@lists.sourceforge.net; Sat, 06 Jun 2015 00:12:16 +0000 Received: by laar3 with SMTP id r3so15209571laa.3 for ; Fri, 05 Jun 2015 17:12:08 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.28.97 with SMTP id a1mr531442lah.9.1433549528368; Fri, 05 Jun 2015 17:12:08 -0700 (PDT) Received: by 10.152.163.98 with HTTP; Fri, 5 Jun 2015 17:12:08 -0700 (PDT) Date: Fri, 5 Jun 2015 20:12:08 -0400 Message-ID: From: Kristov Atlas To: Bitcoin development mailing list Content-Type: multipart/alternative; boundary=089e0160b7d4680a9e0517ce4231 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (kristovatlas.lists[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z11ig-0007O1-Ty Subject: [Bitcoin-development] Lexicographical Indexing of Transaction Inputs and Outputs X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2015 00:12:16 -0000 --089e0160b7d4680a9e0517ce4231 Content-Type: text/plain; charset=UTF-8 Hello all, I have written a draft of a BIP to standardize the sorting of tx inputs and outputs for privacy and security reasons. A few colleagues have reviewed this and provided feedback privately, but now it's ready for feedback from a wider audience. If there is positive sentiment about the proposal after feedback is integrated, I aim for a bip number to be assigned and have it accepted into https://github.com/bitcoin/bips Link: https://github.com/kristovatlas/rfc/blob/master/bips/bip-li01.mediawiki For your convenience, here's the abstract: "Currently there is no standard for bitcoin wallet clients when ordering transaction inputs and outputs. As a result, wallet clients often have a discernible blockchain fingerprint, and can leak private information about their users. By contrast, a standard for non-deterministic sorting could be difficult to audit. This document proposes deterministic lexicographical sorting, using hashes of previous transactions and output indices to sort transaction inputs, as well as value and locking scripts to sort transaction outputs." Thanks, Kristov Atlas Open Bitcoin Privacy Project Contributor, Blockchain.info Security Engineer, etc. Twitter: @kristovatlas Blog: kristovatlas.com --089e0160b7d4680a9e0517ce4231 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello all,

=
I have written a draft of a BIP to standardize the sorting of tx inpu= ts and outputs for privacy and security reasons. A few colleagues have revi= ewed this and provided feedback privately, but now it's ready for feedb= ack from a wider audience.

If there is positive sentiment abou= t the proposal after feedback is integrated, I aim for a bip number to be a= ssigned and have it accepted into https://github.com/bitcoin/bips

Link: https://githu= b.com/kristovatlas/rfc/blob/master/bips/bip-li01.mediawiki

For your convenience, here's the abstract:

"Currently ther= e is no standard for bitcoin wallet clients when ordering transaction input= s and outputs. As a result, wallet clients often have a discernible blockch= ain fingerprint, and can leak private information about their users. By con= trast, a standard for non-deterministic sorting could be difficult to audit= . This document proposes deterministic lexicographical sorting, using hashe= s of previous transactions and output indices to sort transaction inputs, a= s well as value and locking scripts to sort transaction outputs."
<= br>
Thanks,

Kristov Atlas
Open Bitcoin Privacy P= roject Contributor, Blockchain.info Security Engineer, etc.
Twitte= r: @kristovatlas
Blog: kristov= atlas.com
--089e0160b7d4680a9e0517ce4231--