summaryrefslogtreecommitdiff
path: root/c1/06c991ebe5cf07f2880c97acc598eb349873d6
blob: f212cc5bb9a3cd68be775b6bc5fdbf0eeff07a5f (plain)
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jtimon@monetize.io>) id 1UPxrO-00005i-1R
	for bitcoin-development@lists.sourceforge.net;
	Wed, 10 Apr 2013 16:26:58 +0000
Received: from mail-lb0-f179.google.com ([209.85.217.179])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UPxrL-0001xL-TV
	for bitcoin-development@lists.sourceforge.net;
	Wed, 10 Apr 2013 16:26:58 +0000
Received: by mail-lb0-f179.google.com with SMTP id t1so730047lbd.10
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 10 Apr 2013 09:26:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-received:x-originating-ip:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding:x-gm-message-state;
	bh=TKBtQBeJcU/pGiJbOoq+AbML5iRd8uQyPfysHeVN3xQ=;
	b=BKTexewbA7gR9nGAZlIEF5x8DAWSW1DQvjSfZLZ882lIUlT0n2I5nuL0WnM7khyeLb
	gGGwQTlmSZ83a8Lfu+xr3nuvwH/iY2Orh2tjvG77B8G8tFhaZmKLttVvOBF7UOqu7SwO
	JjB31W5tj4u/1zxvJlqZixOF/b3l/okSKJtEvl0agTTJ0m4/5BOQXNLxh8XxPXD6pgwU
	Lfgso+T+wHy8XDUuWGkkPCzbuYGkBtJ29lXGHUOly9nIEUJloJ/OvfX9wGMEXfRkFAQ5
	39bgx2jTg8cv9fGQ4Kb4z14LchHlSPKLsUf1vc2qziFapaU7epDNsdu6yfhLt5+of/dU
	NEUA==
MIME-Version: 1.0
X-Received: by 10.152.132.170 with SMTP id ov10mr1345690lab.21.1365609490886; 
	Wed, 10 Apr 2013 08:58:10 -0700 (PDT)
Received: by 10.112.75.100 with HTTP; Wed, 10 Apr 2013 08:58:10 -0700 (PDT)
X-Originating-IP: [94.126.240.2]
In-Reply-To: <20130410030831.GA12447@savin>
References: <CAAS2fgSkiqfhJxHJNw8i8G5yd1XY6tUTDynQ+AekbwmHP_jZmw@mail.gmail.com>
	<20130410030301.GA9921@savin> <20130410030831.GA12447@savin>
Date: Wed, 10 Apr 2013 17:58:10 +0200
Message-ID: <CAC1+kJOM=QrK4w5O-sqH=CV30v7KCxBZPBS9c+p12XK5UsJ2iw@mail.gmail.com>
From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <jtimon@monetize.io>
To: Peter Todd <pete@petertodd.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnofgDglnrkEm3CoS/uuu/QJl/fFHhRFQVAv4Zg+RddhLqCdH09ERS9ZRNobUAxjIjqtOVM
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1UPxrL-0001xL-TV
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development]
	=?windows-1252?q?To_prevent_arbitrary_data_?=
	=?windows-1252?q?storage_in_txouts_=97_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 16:26:58 -0000

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.

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?

--=20
Jorge Tim=F3n

http://freico.in/