From: bgroff@lavabit•com
To: "Gavin Andresen" <gavinandresen@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Development priorities
Date: Thu, 16 Jun 2011 23:05:59 -0400 (EDT) [thread overview]
Message-ID: <14784.137.56.163.46.1308279959.squirrel@lavabit.com> (raw)
In-Reply-To: <BANLkTimZ5j7=1G89uRO9f7fHPdmDMpLMqg@mail.gmail.com>
> 1) Scaling-up issues, like disconnections when downloading the block
> chain.
>
> 2) Wallet security.
>
> 3) Unit testing framework. There was a PULL that had the start of
> boost unit tests; I think that is a critical need, along with a good
> suite of test cases.
I agree that these are critical and I'd love to help, especially on #2 and
#3. #3 will, by necessity, include a thorough review of the code, which
may uncover latent issues.
I think that for #2 it would also be good to publish a "Best security
practices" document to try and educate the user base.
> Those are the big issues for me. Anything that slows those down I'm
> going to ignore (example: love the idea of escrow transactions, but I
> do NOT want to add nifty new features when we're having trouble
> keeping the features we're using now working properly).
That is understandable. However, something to think about later is that
multi-signature coins can help with #2, even with compromised end-user
machines.
--
Bobby Groff
next prev parent reply other threads:[~2011-06-17 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 16:32 Gavin Andresen
2011-06-16 17:12 ` Luke-Jr
2011-06-16 17:59 ` Jeff Garzik
2011-06-16 18:18 ` Luke-Jr
2011-06-16 18:24 ` phantomcircuit
2011-06-17 3:05 ` bgroff [this message]
2011-06-19 14:26 ` Mike Hearn
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=14784.137.56.163.46.1308279959.squirrel@lavabit.com \
--to=bgroff@lavabit$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/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