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
|
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 0DD11990
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Sep 2016 21:56:53 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148102.authsmtp.net (outmail148102.authsmtp.net
[62.13.148.102])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 5B77115E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Sep 2016 21:56:52 +0000 (UTC)
Received: from mail-c247.authsmtp.com (mail-c247.authsmtp.com [62.13.128.247])
by punt20.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u8KLumZx016284;
Tue, 20 Sep 2016 22:56:48 +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 u8KLukhK030582
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Tue, 20 Sep 2016 22:56:47 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 1D6514016F;
Tue, 20 Sep 2016 21:53:03 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id 0741820306; Tue, 20 Sep 2016 17:56:45 -0400 (EDT)
Date: Tue, 20 Sep 2016 17:56:44 -0400
From: Peter Todd <pete@petertodd.org>
To: Tom <tomz@freedommail.ch>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20160920215644.GA12030@fedora-21-dvm>
References: <7844645.RLYLWYmWtM@garp>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o"
Content-Disposition: inline
In-Reply-To: <7844645.RLYLWYmWtM@garp>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: 2067c6fe-7f7d-11e6-bcde-0015176ca198
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAIUC1AEAgsB AmAbWVZeVVt7XWQ7 bghPaBtcak9QXgdq
T0pMXVMcUQ0TfVla XmUeURl3fwcIfHZx ZQhgXnZcD0IsIFt6
FEkACGwHMGF9OjNL BV1YdwJRcQRMLU5E Y1gxNiYHcQ5VPz4z
GA41ejw8IwAXEilM XwwWMVMUTg4hPwZ0 TgsZHDopGEADW3Z7
ARgrOl8WGEtZDl87 N0AoUk4ZNBkJTGUA
X-Authentic-SMTP: 61633532353630.1038: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
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: Tue, 20 Sep 2016 21:56:53 -0000
--IS0zKkzwUGydFO0o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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.
If the order of the tokens is fixed, the tokens themselves are redundant
information when tokens are required; when tokens may be omitted, a simple
"Some/None" flag to mark whether or not the optional data has been omitted =
is
appropriate.
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
https://petertodd.org 'peter'[:-1]@petertodd.org
--IS0zKkzwUGydFO0o
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJX4bCYAAoJEGOZARBE6K+yoaoH/0pehknnlP2LfTCWfF/UmhJW
T7SBd5ou+a0mrOb7MCiZ2MDXvrNehyyDBeXSANWZjI3y3RnlUgHyTcQp2sh381EP
MMG2GXdfcfWzP8eXRAF+hiuFYKMEOIrqoU60/VzAKSz7IxYds8Y+Piz8ujXpxEWQ
q+Ss4SvKYl+r6qRJ96D4sL/CAjx+JyLFW7WIqyMz0SeFX1nUdMssVrhGwx7fJCL9
LB1pp+oENNLaJeMfOJD76zRXfR6oP8mqTVvsbTYg4kenTLL5yIrXPgTUta8FmBx8
boyp+me4Gs0t841Hs/FArDDlHdxegL1EVQUHDTGscFUGb7QCSc74YDV8owhNJtc=
=mrru
-----END PGP SIGNATURE-----
--IS0zKkzwUGydFO0o--
|
