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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1UQFf1-0006l0-Sh
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Apr 2013 11:27:23 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.113 as permitted sender)
client-ip=62.13.148.113; envelope-from=pete@petertodd.org;
helo=outmail148113.authsmtp.com;
Received: from outmail148113.authsmtp.com ([62.13.148.113])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1UQFez-0008Lo-W7 for bitcoin-development@lists.sourceforge.net;
Thu, 11 Apr 2013 11:27:23 +0000
Received: from mail-c226.authsmtp.com (mail-c226.authsmtp.com [62.13.128.226])
by punt10.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
r3BBREmG025662; Thu, 11 Apr 2013 12:27:14 +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 r3BBR9bo088110
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Thu, 11 Apr 2013 12:27:11 +0100 (BST)
Date: Thu, 11 Apr 2013 07:27:08 -0400
From: Peter Todd <pete@petertodd.org>
To: Jorge =?iso-8859-1?Q?Tim=F3n?= <jtimon@monetize.io>
Message-ID: <20130411112708.GA1006@savin>
References: <CAAS2fgSkiqfhJxHJNw8i8G5yd1XY6tUTDynQ+AekbwmHP_jZmw@mail.gmail.com>
<20130410030301.GA9921@savin> <20130410030831.GA12447@savin>
<CAC1+kJOM=QrK4w5O-sqH=CV30v7KCxBZPBS9c+p12XK5UsJ2iw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz"
Content-Disposition: inline
In-Reply-To: <CAC1+kJOM=QrK4w5O-sqH=CV30v7KCxBZPBS9c+p12XK5UsJ2iw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: c135728a-a29a-11e2-98a9-0025907ec6c5
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdwMUGUUGAgsB AmUbWlZeUlp7WGE7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqAm5z ZBdMDRl6fwRHeDBx ZE9kVj4IXUd/ckR1
E1MFF2RXeGZhPWIC WUgJfh5UcAFPdx9C PwN5B3ZDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA43GXZp EA0eE3B/SnRSXz8+
eElEYgtLAVofdxVl CAw/VFQEBBYIAAxC BUhXERhVLkUIcDE3
ChlTUkMpETtqXTdb HwEzFUgdSmkFRzZW QRsSYUZTDAh4B3wA
dDZQMGUQCEQoIks2 P2wkNgUsBxw5TXIA
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: 1UQFez-0008Lo-W7
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: Thu, 11 Apr 2013 11:27:24 -0000
--3V7upXqbjpZ4EhLz
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 10, 2013 at 05:58:10PM +0200, Jorge Tim=F3n wrote:
> On 4/10/13, Peter Todd <pete@petertodd.org> wrote:
> > Oh, and while we're at it, long-term (hard-fork) it'd be good to change
> > the tx hash algorithm to extend the merkle tree into the txouts/txins
> > itself, which means that to prove a given txout exists you only need to
> > provide it, rather than the full tx.
> >
> > Currently pruning can't prune a whole tx until every output is spent.
> > Make that change and we can prune tx's bit by bit, and still be able to
> > serve nodes requesting proof of their UTXO without making life difficult
> > for anyone trying to spent old UTXO's. The idea is also part of UTXO
> > proof stuff anyway.
>=20
> I thought about this before, I like the idea very much.
> Would such a fork be controversial for anyone?
> Would anyone oppose to this for some reason I'm missing?
You mean https://bitcointalk.org/index.php?topic=3D137933.0 ?
I would oppose it, and I wrote the above proposal. The code required to
implement UTXO fraud proofs is more complex than the entire Bitcoin code
base; obviously that much new fork-critical code opens up huge technical
risks. As an example, can you think of how UTXO fraud proofs can cause
an arbitrarily deep re-org?
--=20
'peter'[:-1]@petertodd.org
--3V7upXqbjpZ4EhLz
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJRZp4MAAoJEH+rEUJn5PoEfpAH/10lKhcSzuBUMdtFJwzh5l6z
O65sAp86p6LsjsrIJlCUAV74KHUb17czFhtfObRRYxxE07INSBWF0dGLqbdf8hOK
vd9jnFHGHIocW41pD4Z9PAZne4Oe2nCri3Yg6tnOcuX5sH4UCyhoIyFamaoMz3Ux
7KYddTrIX4+Ga5M+pZ6LECT/0XE7J0w1JQ1AUYISxuxOm2HfmcXRZX0k8ctGrIsb
t0OV3jkJZH8FQ7AOzhdUC1omJnxkXfsly3Nyc0Dv8uGzhvULKvl+kHII0sK6AUBu
YSFvkE7f9naw8ROsBzBOx2qeP9R2SJMigeTmzeCar3xxxudBR1ayEC+OLNQkiDY=
=hm7o
-----END PGP SIGNATURE-----
--3V7upXqbjpZ4EhLz--
|
