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 <gmaxwell@gmail.com>) id 1UsH8u-0007G2-SN
	for bitcoin-development@lists.sourceforge.net;
	Thu, 27 Jun 2013 18:42:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.182 as permitted sender)
	client-ip=209.85.217.182; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f182.google.com; 
Received: from mail-lb0-f182.google.com ([209.85.217.182])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UsH8s-0003jX-Oy
	for bitcoin-development@lists.sourceforge.net;
	Thu, 27 Jun 2013 18:42:04 +0000
Received: by mail-lb0-f182.google.com with SMTP id r11so597620lbv.27
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 27 Jun 2013 11:41:56 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.88.42 with SMTP id bd10mr4817609lab.32.1372358516086;
	Thu, 27 Jun 2013 11:41:56 -0700 (PDT)
Received: by 10.112.160.104 with HTTP; Thu, 27 Jun 2013 11:41:56 -0700 (PDT)
In-Reply-To: <201306271804.51009.luke@dashjr.org>
References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
	<CAJHLa0Ncac9Xt-AQBnpghqqpfR-j6Xtd9qVQoUe2dPp0kJvz1A@mail.gmail.com>
	<201306271804.51009.luke@dashjr.org>
Date: Thu, 27 Jun 2013 11:41:56 -0700
Message-ID: <CAAS2fgRE+gj0NrDMk-WamSU+mADJM1EqgR-6Sa2MNCbwq-0Gdw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.0 (-)
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.6 URIBL_SBL Contains an URL listed in the SBL blocklist
	[URIs: dashjr.org]
X-Headers-End: 1UsH8s-0003jX-Oy
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop
 client on bitcoin.org
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: Thu, 27 Jun 2013 18:42:05 -0000

On Thu, Jun 27, 2013 at 11:04 AM, Luke-Jr <luke@dashjr.org> wrote:
> On Thursday, June 27, 2013 5:30:21 PM Jeff Garzik wrote:
>> * Very real possibility of an overall net reduction of full nodes on P2P
>> network
> Even a reduction of *nodes at all*, as I've never seen a listening bitcoinj or
> MultiBit node. :/
> Jim, will MultiBit be adding p2p listening support?

Without validation listening isn't currently very useful. :( Maybe it
could be somewhat more with some protocol additions.