Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <wendel@314t.com>) id 1V7r5x-0002Am-IN
	for bitcoin-development@lists.sourceforge.net;
	Fri, 09 Aug 2013 18:07:26 +0000
X-ACL-Warn: 
Received: from mail-we0-f177.google.com ([74.125.82.177])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1V7r5w-0002rR-4U
	for bitcoin-development@lists.sourceforge.net;
	Fri, 09 Aug 2013 18:07:25 +0000
Received: by mail-we0-f177.google.com with SMTP id m46so3655161wev.8
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 09 Aug 2013 11:07:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=x-gm-message-state:sender:subject:mime-version:content-type:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id:references
	:to; bh=gJsyiJGqT2S33CG8174spudpvVMicvobdyDxo2I/7vc=;
	b=QCPupxznCNezYe3469BfPIncVy7IFWZJsYrYToz4y6w+96+zb4COg+4wFMPvMpQPcp
	c2u1xZ0DSrhVc6ybSX12AvsXiIf+NFjeYesxs74yvbfzWdhI6C4zxGjYKdj4I2lvVz5b
	1TQWlEyfY9BEFHgZZtFRApd69x59T/pCgNn6oE1qQac2EHHvZUJILYH2uQKW2FgV5Ml3
	7GjnKQqBCXOkXb5nAt8fkGLrYNxRhfUbaWptgcirrDMxeKczrFzCAASrw7PsqiGFkrkq
	ehsPKKFAOauYaMjLO1ZBjRUmVViNiYhELqSM3pCeeoIDSXrMytLoHxVxXIQL8meBqe67
	K18g==
X-Gm-Message-State: ALoCoQnq/BaXZ9NiexDqPXMxLVpl6XkdG/lXKRxnHFfFbAojdtSiSyr3jK+GssZgClsn8VXTqJL7
X-Received: by 10.180.188.49 with SMTP id fx17mr923055wic.49.1376071151637;
	Fri, 09 Aug 2013 10:59:11 -0700 (PDT)
Received: from [127.0.0.1] ([82.221.102.245])
	by mx.google.com with ESMTPSA id a8sm4061370wie.6.2013.08.09.10.59.06
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 09 Aug 2013 10:59:10 -0700 (PDT)
Sender: w grabhive <wendel@314t.com>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Wendell <w@grabhive.com>
In-Reply-To: <CAJHLa0NxcRHP+hoa1Drie6gfLqCJpnB17+0QsYVO6KQ7gZzYqA@mail.gmail.com>
Date: Fri, 9 Aug 2013 19:58:23 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <703284F8-88EE-4CF1-A78C-CE0DBC88A16F@grabhive.com>
References: <B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com>
	<CAJHLa0NxcRHP+hoa1Drie6gfLqCJpnB17+0QsYVO6KQ7gZzYqA@mail.gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
X-Mailer: Apple Mail (2.1283)
X-Spam-Score: 3.4 (+++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.5 RCVD_IN_PSBL           RBL: Received via a relay in PSBL
	[82.221.102.245 listed in psbl.surriel.com]
	1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
	[Blocked - see <http://www.spamcop.net/bl.shtml?82.221.102.245>]
	0.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server
	[82.221.102.245 listed in dnsbl.sorbs.net]
X-Headers-End: 1V7r5w-0002rR-4U
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] SPV client in pure JavaScript?
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: Fri, 09 Aug 2013 18:07:26 -0000

No, it's not -- but that's certainly very cool to see Jeff.

How is BitPay going to put this to use?

-wendell

grabhive.com | twitter.com/grabhive | gpg: 6C0C9411

On Aug 9, 2013, at 3:08 PM, Jeff Garzik wrote:

> Certainly.  BitPay is working on such a wallet:
> https://github.com/jgarzik/wally
> 
> wally uses node.js JavaScript, and not browser JavaScript, so not
> exactly what you're talking about...