From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z4c9O-0008BW-M0 for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 21:42:38 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of ozlabs.org designates 103.22.144.67 as permitted sender) client-ip=103.22.144.67; envelope-from=rusty@ozlabs.org; helo=ozlabs.org; Received: from ozlabs.org ([103.22.144.67]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Z4c9L-0003Uj-9W for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 21:42:38 +0000 Received: by ozlabs.org (Postfix, from userid 1011) id 7F6DE14029E; Tue, 16 Jun 2015 07:42:27 +1000 (AEST) From: Rusty Russell To: Kristov Atlas , Bitcoin development mailing list In-Reply-To: References: User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Tue, 16 Jun 2015 07:12:14 +0930 Message-ID: <877fr4ejih.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -2.0 (--) 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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Z4c9L-0003Uj-9W Subject: Re: [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: Mon, 15 Jun 2015 21:42:38 -0000 Kristov Atlas writes: > 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 OK, I've modified my implementation to match your proposal: https://github.com/rustyrussell/bitcoin/tree/bip-69 It compiles, and is fairly trivial, but will need some testing. Cheers, Rusty.