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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 5EFD6A1C
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 22 Sep 2016 18:26:25 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail149101.authsmtp.com (outmail149101.authsmtp.com
[62.13.149.101])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 79E6F1AA
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 22 Sep 2016 18:26:24 +0000 (UTC)
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
by punt24.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u8MIQMa6039305;
Thu, 22 Sep 2016 19:26:22 +0100 (BST)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u8MIQJ04034087
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Thu, 22 Sep 2016 19:26:20 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 5AFC8400E2;
Thu, 22 Sep 2016 18:22:34 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id 34E0E202D6; Thu, 22 Sep 2016 14:26:18 -0400 (EDT)
Date: Thu, 22 Sep 2016 14:26:18 -0400
From: Peter Todd <pete@petertodd.org>
To: Tom <tomz@freedommail.ch>
Message-ID: <20160922182618.GA19147@fedora-21-dvm>
References: <7844645.RLYLWYmWtM@garp> <20160920215644.GA12030@fedora-21-dvm>
<5590176.JJpBoGr4Tc@garp>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62"
Content-Disposition: inline
In-Reply-To: <5590176.JJpBoGr4Tc@garp>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: 0f152897-80f2-11e6-829e-00151795d556
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAAUC1AEAgsB AmAbWl1eUlt7W2M7 bghPaBtcak9QXgdq
T0pMXVMcUQ0VeH17 BhoeUR1yfwIIf3x1 YQhiCHFeXkxzclt1
QhhWCGwHMGF9YGIW BV1YdwJRcQRDe0tA b1YxNiYHcQ5VPz4z
GA41ejw8IwAXEilM XwwWMVMUTg4hPwZ0 TgsZHDopGEADW3Z7
ARgrOl8WGEtZDl87 N0AoUk4ZNBkJTGUA
X-Authentic-SMTP: 61633532353630.1037:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
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 <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: Thu, 22 Sep 2016 18:26:25 -0000
--+QahgC5+KEYLbs62
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Sep 21, 2016 at 11:32:33AM +0200, Tom wrote:
> Thanks for your email Peter!
>=20
> 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 for=
the
> > > transaction to be well-formatted. Not serializing transactions in the
> > > order specified would allow multiple interpretations of the data which
> > > can't be allowed.
> >=20
> > If the order of the tokens is fixed, the tokens themselves are redundant
> > information when tokens are required; when tokens may be omitted, a sim=
ple
> > "Some/None" flag to mark whether or not the optional data has been omit=
ted
> > is appropriate.
>=20
> This is addressed in the spec;=20
> https://github.com/bitcoinclassic/documentation/blob/master/spec/transact=
ionv4.md
>=20
> =ABThe way towards that flexibility is to use a generic concept made popu=
lar
> 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 fiel=
ds
> can be omitted from individual transactions=BB
That argument is not applicable to required fields: the code to get the fie=
lds
=66rom the extensible format is every bit as complex as the very simple code
required to deserialize/serialize objects in the current system.
In any case your BIP needs to give some explicit examples of hypothetical
upgrades in the future, how they'd take advantage of this, and what the cod=
e to
do so would look like.
> > Also, if you're going to break compatibility with all existing software=
, it
> > makes sense to use a format that extends the merkle tree down into the
> > transaction inputs and outputs.
>=20
> Please argue your case.
See my arguments re: segwit a few months ago, e.g. the hardware wallet txin
proof use-case.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--+QahgC5+KEYLbs62
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJX5CJHAAoJEGOZARBE6K+yfxcH/1a0I8VlQfPST386Kw6n8jgw
1MQlfL7N8X/P7X9nss/B/TNveaTuwi9/5M3fMxPF/zoBbFOOBszkNmqYaD2ONdak
rGlouZnQ3CJpQzQrScLwHQ5tNHVL9E6VXBrg4XIkbu2PEMZHDVyWTjHGT6R9+Zvc
oLJvq5XDZwp/rACv+FCAcGNjXrEXq7kKHgz/SuRWw+ejTDhrXmJDRb9NNgrAX5eX
CFQZtWWy1pAboJRkEP+dpn/aA0gDo5rJpWKnzdmSWK1UyWlUlKh3agvhuMqZwLOZ
ghs+QgcnwTIAM3XDtXKU6Xc72RAxJX2NR07+N+2ggr9TIBBxSmpmwf2BXGRrpx4=
=Vl/E
-----END PGP SIGNATURE-----
--+QahgC5+KEYLbs62--
|
