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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1UPouX-0008D1-U7
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Apr 2013 06:53:38 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.108 as permitted sender)
client-ip=62.13.148.108; envelope-from=pete@petertodd.org;
helo=outmail148108.authsmtp.net;
Received: from outmail148108.authsmtp.net ([62.13.148.108])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1UPouR-0005lz-Gs for bitcoin-development@lists.sourceforge.net;
Wed, 10 Apr 2013 06:53:37 +0000
Received: from mail-c226.authsmtp.com (mail-c226.authsmtp.com [62.13.128.226])
by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
r3A6rONS041422; Wed, 10 Apr 2013 07:53:24 +0100 (BST)
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r3A6rH3V032635
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Wed, 10 Apr 2013 07:53:19 +0100 (BST)
Date: Wed, 10 Apr 2013 02:53:16 -0400
From: Peter Todd <pete@petertodd.org>
To: Gregory Maxwell <gmaxwell@gmail.com>
Message-ID: <20130410065316.GA31965@savin>
References: <CAAS2fgSkiqfhJxHJNw8i8G5yd1XY6tUTDynQ+AekbwmHP_jZmw@mail.gmail.com>
<20130410030301.GA9921@savin>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI"
Content-Disposition: inline
In-Reply-To: <20130410030301.GA9921@savin>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 544681ca-a1ab-11e2-98a9-0025907ec6c5
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdwIUGUUGAgsB AmUbW1NeVV57WGo7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqAm0H RGYdNBlxdQNFfTB3 YU9mEHVfWEJydBUs
Xx9VRD8bZGY1an0W WBFRagNUcgZDfhgQ OVYsUT1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCXoMVmtr WgwMWGV4JBodXShk
en5ufwkBAEhUYhIL ZkUsX04vOgUYCxFE FltcNyNQO1A2XDYs
FwpVUHkfFgpBUSBB HgYfdUoAV2tPRiQd VBxvHE0IIB4SBWF0
SDs/GhApEFksLl4n eh8YNRwtGho4IwAA
X-Authentic-SMTP: 61633532353630.1020:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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_PASS SPF: sender matches SPF record
X-Headers-End: 1UPouR-0005lz-Gs
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development]
=?utf-8?q?To_prevent_arbitrary_data_storage?=
=?utf-8?q?_in_txouts_=E2=80=94_The_Ultimate_Solution?=
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 06:53:38 -0000
--+HP7ph2BbKc20aGI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Apr 09, 2013 at 11:03:01PM -0400, Peter Todd wrote:
> On Tue, Apr 09, 2013 at 07:53:38PM -0700, Gregory Maxwell wrote:
>=20
> Note how we can already do this: P2SH uses Hash160, which is
> RIPE160(SHA256(d)) We still need a new P2SH *address* type, that
> provides the full 256 bits, but no-one uses P2SH addresses yet anyway.
We can keep the length 160bits:
scriptPubKey: OP_HASH160 OP_HASH160 <Hash160(P2SHv2 address)> OP_EQUALVERIFY
You don't need to change the address type at all if new software is
written to check for both forms of txout in the actual
blockchain/transaction code at the deeper level. Basically now a P2SH
address could actually mean one of two scriptPubKey forms, must like a
normal address can mean either the hashed or bare OP_CHECKSIG form.
Of course, either way you have the odd side-effect that it's now
difficult to pay further funds to a random txout seen on the
blockchain... strange, although possibly not a bad thing.
--=20
'peter'[:-1]@petertodd.org
--+HP7ph2BbKc20aGI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEbBAEBAgAGBQJRZQxbAAoJEH+rEUJn5PoEvZIH+OERYVH3oIJrFEowUcwdO/z0
kYVpVkKGNzswiVPMv7uL6DAyN1dpjXNQ5sX7lSaLdCgZodpVqjiBD3xglbhsBxxl
MbaYwCmVM3vbDEiFweOqy8qzYyubjx2ekoL7vLMnoYvVuggnjA9Hl55xyEoMRhqf
X70w1fLhjPYQrCT3K3jKMfBvG5tAdSz1SeXiJ7t2HEqA7MBh+w8AGrvVTrn+6mql
OWXfaCgE3LNIfaknMUZBceRftPWzrWkTxa9fEMeBa8nT4jCsU7e4dYMNJ9CaF67V
RWlJqTqeQJuaAwqDOeytxTqsZVMNu70DhM0ubypko+0aEaLDfTgjaQBJ99xyTQ==
=ScyD
-----END PGP SIGNATURE-----
--+HP7ph2BbKc20aGI--
|
