From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UVX8B-00040I-8K for bitcoin-development@lists.sourceforge.net; Fri, 26 Apr 2013 01:07:19 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.83.49 as permitted sender) client-ip=74.125.83.49; envelope-from=gavinandresen@gmail.com; helo=mail-ee0-f49.google.com; Received: from mail-ee0-f49.google.com ([74.125.83.49]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UVX86-0000wP-54 for bitcoin-development@lists.sourceforge.net; Fri, 26 Apr 2013 01:07:19 +0000 Received: by mail-ee0-f49.google.com with SMTP id d4so1472823eek.8 for ; Thu, 25 Apr 2013 18:07:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.15.26.6 with SMTP id m6mr47064443eeu.4.1366938427824; Thu, 25 Apr 2013 18:07:07 -0700 (PDT) Received: by 10.223.96.132 with HTTP; Thu, 25 Apr 2013 18:07:07 -0700 (PDT) In-Reply-To: References: <20130425095855.GA30535@crunch> <20130425102853.GA31573@crunch> Date: Thu, 25 Apr 2013 21:07:07 -0400 Message-ID: From: Gavin Andresen To: Jeremy Spilman Content-Type: multipart/alternative; boundary=089e0168144c6bc97204db392788 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1UVX86-0000wP-54 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Cold Signing Payment Requests X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 01:07:19 -0000 --089e0168144c6bc97204db392788 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Apr 25, 2013 at 3:12 PM, Jeremy Spilman wrote: > Right now I'm leaning towards writing a prototype using a single cert with > a fingerprint of PubKey in the Subject Alternate Name, and getting PubKey > and InvoiceID in the Payment Request. Gavin, would the best way to work on > this be to just fork your code on Github? > As usual, our bottleneck is code review / testing, so it would be nice if you spent some time reviewing code and helping test v0.9 so we can actually ship a v1 sometime in the next several months before you start working on a v2. -- -- Gavin Andresen --089e0168144c6bc97204db392788 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Apr 25, 2013 at 3:12 PM, Jeremy Spilman <jeremy.spilman@gma= il.com> wrote:
Right now I'm leaning towards writing a prototype= using a single cert with a fingerprint of PubKey in the Subject Alternate = Name, and getting PubKey and InvoiceID in the Payment Request. =A0Gavin, wo= uld the best way to work on this be to just fork your code on Github?

As usual, our bottleneck= is code review / testing, so it would be nice if you spent some time revie= wing code and helping test v0.9 so we can actually ship a v1 sometime in th= e next several months before you start working on a v2.

--
--
Gavin Andresen

--089e0168144c6bc97204db392788--