From: bgroff@lavabit•com
To: "Matt Corallo" <bitcoin-list@bluematt•me>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap/schedules
Date: Thu, 11 Aug 2011 13:49:21 -0400 (EDT) [thread overview]
Message-ID: <11231.137.56.163.64.1313084961.squirrel@lavabit.com> (raw)
In-Reply-To: <1312995554.17416.22.camel@BMThinkPad.lan.bluematt.me>
Matt Corallo wrote:
> On Wed, 2011-08-10 at 12:29 -0400, Gavin Andresen wrote:
>> I've been wading through the pull requests and bug lists to figure out
>> a roadmap for the next few months.
>> ...
>> 3. Wallet security. I'd like to get Matt's wallet encryption shipped
>> soon, along with all or part of groffer's Multisign patch (#319 --
>> since that will enable the creation of trojan-resistant secure wallet
>> solutions).
> I was under the impression all that was left on the to-do for 0.4 was
> wallet import/export testing and merge (and a few bug fixes like #453),
> I agree #319 should be pulled sometime soon, but maybe for 0.4 just the
> IsStandard parts in 0.4 as those need to get out first anyway?
I'm not sure splitting the patch this way makes a big difference. The
IsStandard part depends on the construction of the multisign script, which
is what most of the patch does anyway. In other words, if upon further
review the script construction needs to change, IsStandard will change.
So a full review would be better.
Also, with unit test coverage for both this feature and existing
script.cpp code, I'm hoping that this patch is relatively low risk and
actually pays down some existing test debt.
--
Bobby Groff
next prev parent reply other threads:[~2011-08-11 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 16:29 Gavin Andresen
2011-08-10 16:59 ` Matt Corallo
2011-08-10 18:57 ` Pieter Wuille
2011-08-11 11:56 ` Mike Hearn
2011-08-11 17:49 ` bgroff [this message]
2011-08-10 20:41 ` Jeff Garzik
2011-08-11 8:48 ` Matt Corallo
2011-08-11 18:20 ` Rick Wesson
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=11231.137.56.163.64.1313084961.squirrel@lavabit.com \
--to=bgroff@lavabit$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/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