From: Gregory Maxwell <gmaxwell@gmail.com>
To: Robert Backhaus <robbak@robbak.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] To prevent arbitrary data storage in txouts — The Ultimate Solution
Date: Tue, 9 Apr 2013 20:58:40 -0700 [thread overview]
Message-ID: <CAAS2fgQLU8oK_BHbnaE9+BzCcT3y0rSBdmMG5B4roq-Tty0Z8A@mail.gmail.com> (raw)
In-Reply-To: <CA+i0-i8M7B6QkTXgNudF5SyK4BKG9rfDp83RSdnm-1GFViBZiQ@mail.gmail.com>
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 like
> it that this denies the possibility of storing data in the block chain, but
> 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— 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.
prev parent reply other threads:[~2013-04-10 3:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 2:53 [Bitcoin-development] To prevent arbitrary data storage in txouts — The Ultimate Solution Gregory Maxwell
2013-04-10 3:03 ` Peter Todd
2013-04-10 3:08 ` Peter Todd
2013-04-10 15:58 ` Jorge Timón
2013-04-11 11:27 ` Peter Todd
2013-04-10 6:53 ` Peter Todd
2013-04-10 7:15 ` Gregory Maxwell
2013-04-10 7:29 ` Peter Todd
2013-04-10 3:52 ` Robert Backhaus
2013-04-10 3:58 ` Gregory Maxwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAS2fgQLU8oK_BHbnaE9+BzCcT3y0rSBdmMG5B4roq-Tty0Z8A@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=robbak@robbak.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox