From: Wendell <w@grabhive.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] SPV client in pure JavaScript?
Date: Fri, 9 Aug 2013 19:58:23 +0200 [thread overview]
Message-ID: <703284F8-88EE-4CF1-A78C-CE0DBC88A16F@grabhive.com> (raw)
In-Reply-To: <CAJHLa0NxcRHP+hoa1Drie6gfLqCJpnB17+0QsYVO6KQ7gZzYqA@mail.gmail.com>
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...
next prev parent reply other threads:[~2013-08-09 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 11:32 [Bitcoin-development] SPV client in pure JavaScript? Wendell
2013-08-09 11:48 ` Mike Hearn
2013-08-09 12:05 ` Wendell
2013-08-09 12:10 ` Mike Hearn
2013-08-09 12:14 ` Mike Hearn
2013-08-09 13:05 ` Wendell
2013-08-13 5:26 ` Chris Double
2013-08-09 13:08 ` Jeff Garzik
2013-08-09 17:58 ` Wendell [this message]
2013-08-09 18:09 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=703284F8-88EE-4CF1-A78C-CE0DBC88A16F@grabhive.com \
--to=w@grabhive.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@bitpay.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox