From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Development priorities
Date: Thu, 16 Jun 2011 13:12:41 -0400 [thread overview]
Message-ID: <201106161312.43850.luke@dashjr.org> (raw)
In-Reply-To: <BANLkTimZ5j7=1G89uRO9f7fHPdmDMpLMqg@mail.gmail.com>
I'd put wallet security before scaling, but inevitably, I'm not sure there's
too much anyone can do about that. Even if the wallet is encrypted, it just
takes a little more complex code to steal funds if you've infected your
target.
On Thursday, June 16, 2011 12:32:57 PM Gavin Andresen wrote:
> Right! I'm back from the CIA, and trying to ignore all the reporters
> who want to talk with me.
>
> I want to do a quick brain dump on what I think the short-term
> development priorities are. Here's my list:
>
> 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.
>
> 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).
>
> Does everybody agree those are the critical priorities? (try not to
> let this thread wander into a discussion of HOW to do stuff, just WHAT
> the priorities aught to be)
next prev parent reply other threads:[~2011-06-16 17:13 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 [this message]
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
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=201106161312.43850.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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