diff options
| author | Gregory Maxwell <gmaxwell@gmail.com> | 2013-04-09 20:58:40 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2013-04-10 03:58:53 +0000 |
| commit | ed2bedf009f839a3011c3a2b997c11b61f956ecf (patch) | |
| tree | 55062af25d2f8caa4978b0c18ef99faac3fcf0fe | |
| parent | 4e7c9a2c4d10e63f043b01a5b55b8f167be6379e (diff) | |
| download | pi-bitcoindev-ed2bedf009f839a3011c3a2b997c11b61f956ecf.tar.gz pi-bitcoindev-ed2bedf009f839a3011c3a2b997c11b61f956ecf.zip | |
Re: [Bitcoin-development] To prevent arbitrary data storage in txouts — The Ultimate Solution
| -rw-r--r-- | 13/d35cac8cec6c916c7a49c449ab4291db7fe942 | 79 |
1 files changed, 79 insertions, 0 deletions
diff --git a/13/d35cac8cec6c916c7a49c449ab4291db7fe942 b/13/d35cac8cec6c916c7a49c449ab4291db7fe942 new file mode 100644 index 000000000..b7e967eea --- /dev/null +++ b/13/d35cac8cec6c916c7a49c449ab4291db7fe942 @@ -0,0 +1,79 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <gmaxwell@gmail.com>) id 1UPmBR-0003Zi-M1 + for bitcoin-development@lists.sourceforge.net; + Wed, 10 Apr 2013 03:58:53 +0000 +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; +Received: from mail-lb0-f174.google.com ([209.85.217.174]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1UPmBL-00027D-VU + for bitcoin-development@lists.sourceforge.net; + Wed, 10 Apr 2013 03:58:53 +0000 +Received: by mail-lb0-f174.google.com with SMTP id s10so100510lbi.19 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 09 Apr 2013 20:58:41 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.112.42.37 with SMTP id k5mr355567lbl.49.1365566320554; Tue, + 09 Apr 2013 20:58:40 -0700 (PDT) +Received: by 10.112.134.164 with HTTP; Tue, 9 Apr 2013 20:58:40 -0700 (PDT) +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 +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: 1UPmBL-00027D-VU +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?= +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 03:58:53 -0000 + +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. + + |