public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Wendell <w@grabhive.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] SPV client in pure JavaScript?
Date: Fri, 9 Aug 2013 14:09:23 -0400	[thread overview]
Message-ID: <CAJHLa0NGEUkVh=OyrbmvvGgaT8KkQjzPp54Nof0D74N2Epuw5g@mail.gmail.com> (raw)
In-Reply-To: <703284F8-88EE-4CF1-A78C-CE0DBC88A16F@grabhive.com>

On Fri, Aug 9, 2013 at 1:58 PM, Wendell <w@grabhive.com> wrote:
> No, it's not -- but that's certainly very cool to see Jeff.
>
> How is BitPay going to put this to use?

Well, "wally" is just a demo application, a command line client to
prove a technology.

The main development is in places like "node-libcoin", where a wallet
platform is being developed.  While maintaining a strong commitment to
the blockchain engine side of bitcoind, BitPay has enterprise wallet
needs that do not necessarily mesh well with the standard bitcoind
wallet.  Multi-sig, P2SH and other advanced features are key to the
future use of bitcoin in large enterprises.  Managers, CEOs and other
functionaries at a corporation may each have their own wallets /
keyrings, and cooperate to sign large value, high security bitcoin
multi-sig transactions, for example.

-- 
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc.      https://bitpay.com/



      reply	other threads:[~2013-08-09 18:09 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
2013-08-09 18:09     ` Jeff Garzik [this message]

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='CAJHLa0NGEUkVh=OyrbmvvGgaT8KkQjzPp54Nof0D74N2Epuw5g@mail.gmail.com' \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=w@grabhive.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