From: Wendell <w@grabhive.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] SPV client in pure JavaScript?
Date: Fri, 9 Aug 2013 13:32:31 +0200 [thread overview]
Message-ID: <B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
To those of you in the know about modern browser tech:
Does it seem at all conceivable that an SPV wallet could be built entirely in JavaScript? And if indeed it is within the realm of the possible, how would such a thing be safely distributed for use? Would a signed Chrome Plugin be an ideal vehicle?
-wendell
grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next reply other threads:[~2013-08-09 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 11:32 Wendell [this message]
2013-08-09 11:48 ` [Bitcoin-development] SPV client in pure JavaScript? 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
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=B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com \
--to=w@grabhive.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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