Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UPWYE-0003cS-Rz for bitcoin-development@lists.sourceforge.net; Tue, 09 Apr 2013 11:17:22 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of outlook.com designates 65.55.116.17 as permitted sender) client-ip=65.55.116.17; envelope-from=jayf@outlook.com; helo=blu0-omc1-s6.blu0.hotmail.com; Received: from blu0-omc1-s6.blu0.hotmail.com ([65.55.116.17]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UPWYD-0002LU-Qb for bitcoin-development@lists.sourceforge.net; Tue, 09 Apr 2013 11:17:22 +0000 Received: from BLU0-SMTP139 ([65.55.116.8]) by blu0-omc1-s6.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 9 Apr 2013 04:17:16 -0700 X-EIP: [FUPuh1B/FNeDVNFPwixXBfxBCcGLzye/] X-Originating-Email: [jayf@outlook.com] Message-ID: Received: from [192.168.1.15] ([67.189.14.219]) by BLU0-SMTP139.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 9 Apr 2013 04:17:15 -0700 Date: Tue, 9 Apr 2013 04:17:13 -0700 From: Jay F User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Peter Todd References: <20130409110911.GA25700@savin> In-Reply-To: <20130409110911.GA25700@savin> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Apr 2013 11:17:15.0570 (UTC) FILETIME=[CA576920:01CE3513] X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [65.55.116.17 listed in list.dnswl.org] -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 (jayf[at]outlook.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 MSGID_FROM_MTA_HEADER Message-Id was added by a relay X-Headers-End: 1UPWYD-0002LU-Qb Cc: Bitcoin Development Subject: Re: [Bitcoin-development] On-going data spam X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2013 11:17:23 -0000 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.