From: Mike Hearn <mike@plan99•net>
To: slush <slush@centrum•cz>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Version 0.9 goals
Date: Thu, 15 Aug 2013 17:22:23 +0200 [thread overview]
Message-ID: <CANEZrP2+8a4-tp39Cfoi2TvbfGAka3BgAWMdprfmG8rDc6deiw@mail.gmail.com> (raw)
In-Reply-To: <CAJna-HiSUHSAREzGLxi0nUctmt4OoaAKC7txEruQG_AgwGa_Qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
> 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).
>
Yeah, OK. Let's see how much progress Gary makes. Supporting HD wallets is
the trickiest part and I don't know how much time I will have - the Android
RNG issue and getting bcj 0.10 released have sucked up a lot of my time
lately and I need to refocus on other things for a bit. But between the guy
who volunteered to do payment protocol, and Gary doing TrezorJ, and Matija
already having done the core algorithms, I'm hoping the only parts I'll
have to do are integrating the HD code with the core wallet code. Possibly
if we're running out of time I can do a real basic HD wallet implementation
that only iterates a key once and doesn't generate new keys for each
transaction, as that's really the trickiest part (because of the need for
lookahead/behind and memory bloat on phones).
[-- Attachment #2: Type: text/html, Size: 1422 bytes --]
next prev parent reply other threads:[~2013-08-15 15:22 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 [this message]
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=CANEZrP2+8a4-tp39Cfoi2TvbfGAka3BgAWMdprfmG8rDc6deiw@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=slush@centrum$(echo .)cz \
/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