Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E412194E for ; Wed, 21 Sep 2016 09:32:41 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mx-out01.mykolab.com (mx.kolabnow.com [95.128.36.1]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 53A94149 for ; Wed, 21 Sep 2016 09:32:41 +0000 (UTC) X-Virus-Scanned: amavisd-new at kolabnow.com X-Spam-Score: -2.9 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Received: from mx04.mykolab.com (mx04.mykolab.com [10.20.7.102]) by mx-out01.mykolab.com (Postfix) with ESMTPS id C4D7D6161E; Wed, 21 Sep 2016 11:32:38 +0200 (CEST) From: Tom To: Peter Todd Date: Wed, 21 Sep 2016 11:32:33 +0200 Message-ID: <5590176.JJpBoGr4Tc@garp> In-Reply-To: <20160920215644.GA12030@fedora-21-dvm> References: <7844645.RLYLWYmWtM@garp> <20160920215644.GA12030@fedora-21-dvm> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart12395476.uG1dcxR6bD"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Wed, 21 Sep 2016 11:10:52 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Requesting BIP assignment; Flexible Transactions. 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, 21 Sep 2016 09:32:42 -0000 --nextPart12395476.uG1dcxR6bD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Thanks for your email Peter! On Tuesday 20 Sep 2016 17:56:44 Peter Todd wrote: > On Tue, Sep 20, 2016 at 07:15:45PM +0200, Tom via bitcoin-dev wrote: > > =3D=3D=3D Serialization order=3D=3D=3D > >=20 > > The tokens defined above have to be serialized in a certain order f= or the > > transaction to be well-formatted. Not serializing transactions in = the > > order specified would allow multiple interpretations of the data wh= ich > > can't be allowed. >=20 > If the order of the tokens is fixed, the tokens themselves are redund= ant > information when tokens are required; when tokens may be omitted, a s= imple > "Some/None" flag to mark whether or not the optional data has been om= itted > is appropriate. This is addressed in the spec;=20 https://github.com/bitcoinclassic/documentation/blob/master/spec/transa= ctionv4.md =ABThe way towards that flexibility is to use a generic concept made po= pular various decades ago with the XML format. The idea is that we give each field a name and this means that new fields can be added or optional fi= elds can be omitted from individual transactions=BB > Also, if you're going to break compatibility with all existing softwa= re, it > makes sense to use a format that extends the merkle tree down into th= e > transaction inputs and outputs. Please argue your case. --nextPart12395476.uG1dcxR6bD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJX4lO1AAoJEMKlVF6pHMrncAcP/A5XTeNQ+rzu4lX64jl+mtuH 73BOTO6JQ63w89+5vnL4AkRTBy86RJ5Ft7laJUGXcIf26snFF3coLIschNsRcLTc siGyKsBca/xSh/RNpdhOA7waWEHD6FeifIza+wsA+PwY1fSFWw2Mlm2RD3gqzz6q WBecXnwkXBNz9X8p0HC3Uu+MXxYYnnGaZHZ750yXTERwD9pSaCFPhhgWaLQSB+Z3 ljXvy6qkNvkXf+0K4xl+8wMCf82uJiGxax8dc5Pj9P94W+bqekmqFPHHwklJitvc h0ApT3/Y2Nlb0HB+Y2RoQCa9iqfOcDTkaDzcBjgacv95pgFzOSxsSPvlDn1mFV0g gK6doc1xE5mmi97NyjqPTTPRD/3HnaUuxzYp+5pey8S9HQiZS+Tf239jv82u2RCH s2avpeIFNlAnNSdLlbsRvZxpJs+Rez8dGNqkRm9PgIpBPjVsXNA728GeLIV5v79N x7MQ2fLPs22Dd407YhEAk5FIb3oek8ZHMLkyRnIFrVtCip/vuVcLHfWZT5VIiHGj kef9f+uAzYGfjHpZ0LWMlXg544Cbu6RfDdPL7kFz1vVar4hBcIUv+2Sgp6kbqH/x NBApT//HgjckTvrl5Szpgrg0m6cWupFAR4snkUNnAY9eAcC1lB0t/C5hCgJO+Yai urhcWzSnzioaRhtbJxRk =by+Z -----END PGP SIGNATURE----- --nextPart12395476.uG1dcxR6bD--