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 <gmaxwell@gmail.com>) id 1UF9qd-0005IE-1w
	for bitcoin-development@lists.sourceforge.net;
	Mon, 11 Mar 2013 21:01:31 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.48 as permitted sender)
	client-ip=209.85.215.48; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f48.google.com; 
Received: from mail-la0-f48.google.com ([209.85.215.48])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UF9qZ-0002Ms-Os
	for bitcoin-development@lists.sourceforge.net;
	Mon, 11 Mar 2013 21:01:31 +0000
Received: by mail-la0-f48.google.com with SMTP id fq13so4461780lab.35
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 11 Mar 2013 14:01:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.26.202 with SMTP id n10mr5256166lbg.15.1363035680996;
	Mon, 11 Mar 2013 14:01:20 -0700 (PDT)
Received: by 10.112.96.164 with HTTP; Mon, 11 Mar 2013 14:01:20 -0700 (PDT)
In-Reply-To: <EE5395CC-46C4-4C24-AA8F-A4E22FD07693@ceptacle.com>
References: <20130310043155.GA20020@savin>
	<CABOyFfp9Kd+y=SofWfq6TiR4+xeOhFL7VVHWjtrRn83HMsmPBA@mail.gmail.com>
	<CAH2=CKx-SWk17v9uGFAmk=-sbFrxeuvAvCFmECSvM7FEH-C0kw@mail.gmail.com>
	<EE5395CC-46C4-4C24-AA8F-A4E22FD07693@ceptacle.com>
Date: Mon, 11 Mar 2013 14:01:20 -0700
Message-ID: <CAAS2fgRJznqyFuWnhHedA151peVn4K77Bw82ACC1WhnUyCdAqw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Michael Gronager <gronager@ceptacle.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gmaxwell[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UF9qZ-0002Ms-Os
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Blocking uneconomical UTXO creation
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: Mon, 11 Mar 2013 21:01:31 -0000

On Mon, Mar 11, 2013 at 1:36 PM, Michael Gronager <gronager@ceptacle.com> wrote:
> The point with UTXO is in the long run to be able to switch from a p2p network where everyone stores, validates and verifies everything to a DHT where the load of storing, validating and verifying can be shared.

I believe you are confusing disjoint things.