From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VeCdT-0001Dk-HR for bitcoin-development@lists.sourceforge.net; Wed, 06 Nov 2013 23:35:43 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bluematt.me designates 192.241.179.72 as permitted sender) client-ip=192.241.179.72; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from mail.bluematt.me ([192.241.179.72]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VeCdR-0003x0-J0 for bitcoin-development@lists.sourceforge.net; Wed, 06 Nov 2013 23:35:43 +0000 Received: from [10.232.233.22] (vps.bluematt.me [173.246.101.161]) by mail.bluematt.me (Postfix) with ESMTPSA id D93F0496AD; Wed, 6 Nov 2013 23:35:35 +0000 (UTC) Message-ID: <527AD246.9050906@bluematt.me> Date: Wed, 06 Nov 2013 18:35:34 -0500 From: Matt Corallo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: tier.nolan@gmail.com References: <5279D89D.5000609@bluematt.me> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bluematt.me] X-Headers-End: 1VeCdR-0003x0-J0 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] [ANN] High-speed Bitcoin Relay Network 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: Wed, 06 Nov 2013 23:35:43 -0000 No, the transactions relayed are piped through a bitcoind first (ie fully verified by a bitcoind). For blocks, for which the timing needs to be tighter, bitcoinj does SPV-validation. Though it is possible to create a block which passes SPV validation but causes a DoS score, doing so would cost a miner a full block's worth of profits, which they are fairly unlikely to do. In any case, if it every becomes a problem, its not hard to adapt addnode to allow higher DoS scores for individual nodes. Matt On 11/06/13 07:25, Tier Nolan wrote: > > > > On Wed, Nov 6, 2013 at 5:50 AM, Matt Corallo > wrote: > > Relay node details: > * The relay nodes do some data verification to prevent DoS, but in > order to keep relay fast, they do not fully verify the data they are > relaying, thus YOU SHOULD NEVER mine a block building on top of a > relayed block without fully checking it with your own bitcoin validator > (as you would any other block relayed from the P2P network). > > > Wouldn't this cause disconnects due to misbehavior? > > A standard node connecting to a relay node would receive > blocks/transactions that are not valid in some way and then disconnect. > > Have you looked though the official client to find what things are > considered signs that a peer is hostile? I assume things like double > spending checks count as misbehavior and can't be quickly checked by a > relay node. > > Maybe another bit could be assigned in the services field as "relay". > This means that the node doesn't do any checking. > > Connects to relay nodes could be command line/config file only. Peers > wouldn't connect to them.