From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: <20130410030301.GA9921@savin> <20130410030831.GA12447@savin> Date: Wed, 10 Apr 2013 17:58:10 +0200 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= To: Peter Todd 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2013 16:26:58 -0000 On 4/10/13, Peter Todd 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/