Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VjxmV-00072w-BN for bitcoin-development@lists.sourceforge.net; Fri, 22 Nov 2013 20:56:51 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.180 as permitted sender) client-ip=209.85.217.180; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f180.google.com; Received: from mail-lb0-f180.google.com ([209.85.217.180]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VjxmU-0005gm-Jt for bitcoin-development@lists.sourceforge.net; Fri, 22 Nov 2013 20:56:51 +0000 Received: by mail-lb0-f180.google.com with SMTP id w6so1427070lbh.39 for ; Fri, 22 Nov 2013 12:56:43 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.20.6 with SMTP id j6mr11016063lae.8.1385153803872; Fri, 22 Nov 2013 12:56:43 -0800 (PST) Received: by 10.112.63.166 with HTTP; Fri, 22 Nov 2013 12:56:43 -0800 (PST) In-Reply-To: References: Date: Fri, 22 Nov 2013 12:56:43 -0800 Message-ID: From: Gregory Maxwell To: Jeff Garzik Content-Type: text/plain; charset=UTF-8 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 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: bitpay.com] X-Headers-End: 1VjxmU-0005gm-Jt Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] [PATCH, try2] bitcoind: whitelist nodes against banning 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: Fri, 22 Nov 2013 20:56:51 -0000 On Fri, Nov 22, 2013 at 12:49 PM, Jeff Garzik wrote: > Whitelist nodes against banning. Is there a reason not to have a parallel get rpc to get the current list?