From: Wendell <w@grabhive•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Version 0.9 goals
Date: Thu, 15 Aug 2013 23:12:59 +0200 [thread overview]
Message-ID: <71E73F38-0D1D-4446-878C-51229EEA4C59@grabhive.com> (raw)
In-Reply-To: <CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
Mike,
If bitcoinj will be ready and you will help us, we are willing to implement it right away in Hive as well. We will also keep BitcoinKit.framework updated with the new bitcoind and bitcoinj implementations.
BitPay taking the lead here would be tremendous. Hopefully cool sites like Bitcoin Store will also be game to hit the ground running. I'll ask them.
-wendell
grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
On Aug 15, 2013, at 10:09 AM, Mike Hearn wrote:
> Pieter, Matt and I also agreed that for maximum impact we should really try to ship payment protocol support in at least two clients simultaneously and ideally with a big merchant signed up too - to send a powerful message that we really mean it. Someone volunteered last week to do it for bitcoinj and if he doesn't pull through, I have some old code from EOY 2012 that I could update to the latest spec and ship at least some basic support. I'd hope that we can get Bitcoin Wallet or MultiBit updates out once bcj has support pretty fast.
>
> Also, Jeff said that BitPay want to be a leader in support for the protocol. So let's try and co-ordinate release dates so we can make a bit of a splash and grab the ecosystems attention.
next prev parent reply other threads:[~2013-08-15 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 0:29 Gavin Andresen
2013-08-15 8:09 ` Mike Hearn
2013-08-15 8:22 ` slush
2013-08-15 9:02 ` Mike Hearn
2013-08-15 14:32 ` slush
2013-08-15 15:22 ` Mike Hearn
2013-08-15 8:37 ` Pieter Wuille
2013-08-15 21:12 ` Wendell [this message]
2013-08-15 10:12 ` Melvin Carvalho
2013-08-15 10:49 ` Wladimir
2013-08-15 10:56 ` Pieter Wuille
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=71E73F38-0D1D-4446-878C-51229EEA4C59@grabhive.com \
--to=w@grabhive$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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