Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.174 as permitted sender)
	client-ip=209.85.217.174; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f174.google.com; 
MIME-Version: 1.0
In-Reply-To: <CA+i0-i8M7B6QkTXgNudF5SyK4BKG9rfDp83RSdnm-1GFViBZiQ@mail.gmail.com>
References: <CAAS2fgSkiqfhJxHJNw8i8G5yd1XY6tUTDynQ+AekbwmHP_jZmw@mail.gmail.com>
	<CA+i0-i8M7B6QkTXgNudF5SyK4BKG9rfDp83RSdnm-1GFViBZiQ@mail.gmail.com>
Date: Tue, 9 Apr 2013 20:58:40 -0700
Message-ID: <CAAS2fgQLU8oK_BHbnaE9+BzCcT3y0rSBdmMG5B4roq-Tty0Z8A@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Robert Backhaus <robbak@robbak.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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?=
Precedence: list

On Tue, Apr 9, 2013 at 8:52 PM, Robert Backhaus <robbak@robbak.com> wrote:
> That sounds workable. I take it that the P2SH address is not stored? I li=
ke
> it that this denies the possibility of storing data in the block chain, b=
ut
> does not block interesting uses like creating date stamps - You can still
> store the 'fake P2SH' value whose checksum is secured by the blockchain.

Correct. It doesn't prevent value commitment (which is actually what
we need for our currency use), just data storage.

And as Peter points out=E2=80=94 you could try to store a little data, but
that has a computational cost which is exponential in the amount of
data stored per output. ... like storing data in values, thats awkward
enough to not be especially problematic, I expect.