Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VA0Jj-0004hu-DK for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 16:22:31 +0000 X-ACL-Warn: Received: from mail-vb0-f43.google.com ([209.85.212.43]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VA0Ji-00019D-8c for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 16:22:31 +0000 Received: by mail-vb0-f43.google.com with SMTP id h11so730961vbh.2 for ; Thu, 15 Aug 2013 09:22:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=dwv0HAL/Uzw6tf4Ay3Houm/K4yD8s5r5URb15YMvgkY=; b=aokQ+thsGl6PieKJO4eg/GkLfSUb1g/o0i004gguTn1dxRlVW+757lNWTSt0AbQOqX tnMfghc0AnQLGA9r/+MAfEAe8X0ldbbRBx04SmIilLftJp0p0beER13JBnOazEMvVeUF y6VwgUEoEWgMW8f6K4+Jju4omxBM08kfs/stCoeR0axgrozIpjGNGb2k4mJtM1Ieshrp YQFuGsQkueh+znHmnT2AP01hi6j4wQ4YBthJ7y4nv4FkQjJML9iEylTVMUNgqKFP9ze9 uxXBEB4sCE/5LJuNFstcplmyTEBphFFneDY3/wwZFuK4EOcbGXKhUdkcUj23RDZeMd9v XqOw== X-Gm-Message-State: ALoCoQmrVL2kezSDP3LJpbAwfiuTmS3Cwm/AzZ9k6CJ2wye0dOcI/HG3705LMxnO54imBev7N8Lq X-Received: by 10.220.58.5 with SMTP id e5mr97009vch.52.1376577172892; Thu, 15 Aug 2013 07:32:52 -0700 (PDT) MIME-Version: 1.0 Sender: marek@palatinus.cz Received: by 10.58.235.136 with HTTP; Thu, 15 Aug 2013 07:32:22 -0700 (PDT) In-Reply-To: References: From: slush Date: Thu, 15 Aug 2013 16:32:22 +0200 X-Google-Sender-Auth: ZN18THRKLTatbtEFUiiEIQ_3ruQ Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=001a11c2be44657e4604e3fd5986 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slush[at]centrum.cz) 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1VA0Ji-00019D-8c Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Aug 2013 16:22:31 -0000 --001a11c2be44657e4604e3fd5986 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Aug 15, 2013 at 11:02 AM, Mike Hearn wrote: > On Thu, Aug 15, 2013 at 10:22 AM, slush wrote: > >> We're planning to support payment protocol in Trezor as well, if it >> counts. I think it's a missing piece in absolute security of hardware >> wallets. >> > > Yup, that's always been the plan :-) > > Any idea how much work it is, and would it be a v1 feature of the Trezor > or added later via firmware update? > Our plan is to add support for that into v1 firmware, but it also depends on readiness of surrounding infrastructure; mainly if there'll be support for payment protocol in multibit in the time of v1 release (I suppose that the Multibit will be the first wallet compatible with Trezor AND supporting payment protocol). slush --001a11c2be44657e4604e3fd5986 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Thu, Aug 15, 2013 at 11:02 AM, Mike Hearn <mike@plan99.net> wrote:
On Thu, A= ug 15, 2013 at 10:22 AM, slush <slush@centrum.cz> wrote:
We're planning to support payment protocol in Trezor a= s well, if it counts. I think it's a missing piece in absolute security= of hardware wallets.

Yup, = that's always been the plan :-)=A0

Any idea how much work it is, and would it be a v1 feat= ure of the Trezor or added later via firmware update?

Our plan is t= o add support for that into v1 firmware, but it also depends on readiness o= f surrounding infrastructure; mainly if there'll be support for payment= protocol in multibit in the time of v1 release (I suppose that the Multibi= t will be the first wallet =A0compatible with Trezor AND supporting payment= protocol).

slush
--001a11c2be44657e4604e3fd5986--