From: slush <slush@centrum.cz>
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 16:32:22 +0200 [thread overview]
Message-ID: <CAJna-HiSUHSAREzGLxi0nUctmt4OoaAKC7txEruQG_AgwGa_Qw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3-SV0=PB5rkXbAEKv1CFqfS4hjuBTY3YbU-yNGKde8tg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Thu, Aug 15, 2013 at 11:02 AM, Mike Hearn <mike@plan99.net> wrote:
> On Thu, Aug 15, 2013 at 10:22 AM, slush <slush@centrum.cz> 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
[-- Attachment #2: Type: text/html, Size: 1601 bytes --]
next prev parent reply other threads:[~2013-08-15 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 0:29 [Bitcoin-development] Version 0.9 goals 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 [this message]
2013-08-15 15:22 ` Mike Hearn
2013-08-15 8:37 ` Pieter Wuille
2013-08-15 21:12 ` Wendell
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=CAJna-HiSUHSAREzGLxi0nUctmt4OoaAKC7txEruQG_AgwGa_Qw@mail.gmail.com \
--to=slush@centrum.cz \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/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