1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bgroff@lavabit.com>) id 1QXPNl-00026d-Mb
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jun 2011 03:06:05 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of lavabit.com
designates 72.249.41.33 as permitted sender)
client-ip=72.249.41.33; envelope-from=bgroff@lavabit.com;
helo=karen.lavabit.com;
Received: from karen.lavabit.com ([72.249.41.33])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1QXPNk-00052K-Tk for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jun 2011 03:06:05 +0000
Received: from a.earth.lavabit.com (a.earth.lavabit.com [192.168.111.10])
by karen.lavabit.com (Postfix) with ESMTP id 291F611C125;
Thu, 16 Jun 2011 22:05:59 -0500 (CDT)
Received: from lavabit.com (torserver.uvt.nl [137.56.163.46])
by lavabit.com with ESMTP id M7AVN69959JB;
Thu, 16 Jun 2011 22:05:59 -0500
Received: from 137.56.163.46 (SquirrelMail authenticated user bgroff)
by lavabit.com with HTTP; Thu, 16 Jun 2011 23:05:59 -0400 (EDT)
Message-ID: <14784.137.56.163.46.1308279959.squirrel@lavabit.com>
In-Reply-To: <BANLkTimZ5j7=1G89uRO9f7fHPdmDMpLMqg@mail.gmail.com>
References: <BANLkTimZ5j7=1G89uRO9f7fHPdmDMpLMqg@mail.gmail.com>
Date: Thu, 16 Jun 2011 23:05:59 -0400 (EDT)
From: bgroff@lavabit.com
To: "Gavin Andresen" <gavinandresen@gmail.com>
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.4 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
X-Headers-End: 1QXPNk-00052K-Tk
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Development priorities
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 03:06:05 -0000
> 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 an=
d
#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
|
