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 1VA5Fj-0006I2-3J
	for bitcoin-development@lists.sourceforge.net;
	Thu, 15 Aug 2013 21:38:43 +0000
X-ACL-Warn: 
Received: from mail-we0-f175.google.com ([74.125.82.175])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VA5Fh-0006Hz-MM
	for bitcoin-development@lists.sourceforge.net;
	Thu, 15 Aug 2013 21:38:43 +0000
Received: by mail-we0-f175.google.com with SMTP id q58so1037855wes.34
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 15 Aug 2013 14:38:35 -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=l30VAAyjKehuHi7HjcN0kf27ZzCjCyxqNk8JUjneRHs=;
	b=CIt7T/n2VYZ7SbWcLYrCt0SPhnugaLjXF+bi4Z/x5vYsRIjhRYfah8/W0Wo3n6XmGR
	dodSpmLcLd+FIAZ9E5hfw8Q9csrYeA+RywjppwGIJjEnXbzOGFfkJcGV9kg56ApUWYdb
	8EX7eF6VsO9SFSfyATi/RHAr0AXSLu+U2fxrcDbKmPqcLy1wtI67S3EnZ1wezxWsbqkw
	N0Z3asYLg8RKDZ9/crMvQZh0r6r7PNnD+zgF9d7w+9tklSxXTTxzCy1DFvf0BZAB0WJG
	ZdXhyrWmhnHSBL/KnoS/Fg902hG124V8lt+x96wdLgE7sd3p4UV12g/8S518AIpaWb/4
	2vvQ==
X-Gm-Message-State: ALoCoQmQlN3VKquKG7hYzJHMaWeFldG7G5YbMeoT+Y13m7H7c+vQ1NqAaGXoVPK6IWRv/sidF2JR
X-Received: by 10.194.176.163 with SMTP id cj3mr3717123wjc.8.1376601191133;
	Thu, 15 Aug 2013 14:13:11 -0700 (PDT)
Received: from [127.0.0.1] (lns-bzn-51f-81-56-143-198.adsl.proxad.net.
	[81.56.143.198])
	by mx.google.com with ESMTPSA id jf2sm1610147wic.2.2013.08.15.14.13.05
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 15 Aug 2013 14:13:10 -0700 (PDT)
Sender: w grabhive <wendel@314t.com>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Wendell <w@grabhive.com>
In-Reply-To: <CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
Date: Thu, 15 Aug 2013 23:12:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <71E73F38-0D1D-4446-878C-51229EEA4C59@grabhive.com>
References: <CABsx9T3DM72+8HgNWWZ2HaAgZMQGAPn87L9VVKdkbVkS7sd8Tg@mail.gmail.com>
	<CANEZrP3bt40ThBcqWLfzuS5508mpbo4Z5qxh9AJs-FRrk0QJsA@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
X-Mailer: Apple Mail (2.1283)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1VA5Fh-0006Hz-MM
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Version 0.9 goals
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: Thu, 15 Aug 2013 21:38:43 -0000

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.
>=20
> 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.