Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of robbak.com
	designates 74.125.82.176 as permitted sender)
	client-ip=74.125.82.176; envelope-from=robbak@robbak.com;
	helo=mail-we0-f176.google.com; 
MIME-Version: 1.0
In-Reply-To: <BLU0-SMTP1397D392A87B5A2E21636B8C8C60@phx.gbl>
References: <CA+8xBpc5iV=prakWKkNFa0O+tgyhoHxJ9Xwz6ubhPRUBf_95KA@mail.gmail.com>
	<CANEZrP1EKaHbpdC6X=9mvyJHC_cvW7u5p9nqM7EwkEypAg4Xmg@mail.gmail.com>
	<20130409110911.GA25700@savin>
	<BLU0-SMTP1397D392A87B5A2E21636B8C8C60@phx.gbl>
Date: Tue, 9 Apr 2013 21:34:33 +1000
Message-ID: <CA+i0-i-4PJkKPm=j0A0vHY8aTuk5p5xx2J-0uJWAKBgdje137w@mail.gmail.com>
From: Robert Backhaus <robbak@robbak.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7bb03a50faaa9404d9ebef4a
Subject: Re: [Bitcoin-development] On-going data spam
Precedence: list

--047d7bb03a50faaa9404d9ebef4a
Content-Type: text/plain; charset=ISO-8859-1

The obvious problem is that if you can frame it as a valid address, you can
put what you want there. If you can make it pass the validation, miners
have no way of knowing it's not a valid address.

Of course, there is nothing new about this. I ran strings on the blockchain
and found all sorts of ascii rubbish right from the beginning.


On 9 April 2013 21:17, Jay F <jayf@outlook.com> wrote:

> On 4/9/2013 4:09 AM, Peter Todd wrote:
> > On Tue, Apr 09, 2013 at 12:42:12PM +0200, Mike Hearn wrote:
> >> hack by changing the protocol. Nodes can serve up blocks encrypted
> under a
> >> random key. You only get the key when you finish the download. A
> blacklist
> > NAK
> >
> > Makes bringing up a new node dependent on other nodes having consistent
> > uptimes, particularly if you are on a low-bandwidth connection.
> >
> >> can apply to Bloom filtering such that transactions which are known to
> be
> >> "abusive" require you to fully download the block rather than select the
> >> transactions with a filter. This means that people can still access the
> > NAK
> >
> > No blacklists
> >
> It depends on how clever the spammers get encoding stuff. If law
> enforcement forensic tools can pull a jpeg header + child porn out of
> the blockchain, then there's a problem that needs mitigation.
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--047d7bb03a50faaa9404d9ebef4a
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">The obvious problem is that if you can frame it as a valid address, you can put what you want there. If you can make it pass the validation, miners have no way of knowing it&#39;s not a valid address.<div><br>
</div><div style>Of course, there is nothing new about this. I ran strings on the blockchain and found all sorts of ascii rubbish right from the beginning.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 9 April 2013 21:17, Jay F <span dir="ltr">&lt;<a href="mailto:jayf@outlook.com" target="_blank">jayf@outlook.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On 4/9/2013 4:09 AM, Peter Todd wrote:<br>
&gt; On Tue, Apr 09, 2013 at 12:42:12PM +0200, Mike Hearn wrote:<br>
&gt;&gt; hack by changing the protocol. Nodes can serve up blocks encrypted under a<br>
&gt;&gt; random key. You only get the key when you finish the download. A blacklist<br>
&gt; NAK<br>
&gt;<br>
&gt; Makes bringing up a new node dependent on other nodes having consistent<br>
&gt; uptimes, particularly if you are on a low-bandwidth connection.<br>
&gt;<br>
&gt;&gt; can apply to Bloom filtering such that transactions which are known to be<br>
&gt;&gt; &quot;abusive&quot; require you to fully download the block rather than select the<br>
&gt;&gt; transactions with a filter. This means that people can still access the<br>
&gt; NAK<br>
&gt;<br>
&gt; No blacklists<br>
&gt;<br>
</div></div>It depends on how clever the spammers get encoding stuff. If law<br>
enforcement forensic tools can pull a jpeg header + child porn out of<br>
the blockchain, then there&#39;s a problem that needs mitigation.<br>
<div class="HOEnZb"><div class="h5"><br>
------------------------------------------------------------------------------<br>
Precog is a next-generation analytics platform capable of advanced<br>
analytics on semi-structured data. The platform includes APIs for building<br>
apps and a phenomenal toolset for data science. Developers can use<br>
our toolset for easy data analysis &amp; visualization. Get a free account!<br>
<a href="http://www2.precog.com/precogplatform/slashdotnewsletter" target="_blank">http://www2.precog.com/precogplatform/slashdotnewsletter</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br></div>

--047d7bb03a50faaa9404d9ebef4a--