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
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
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 <jgarzik@bitpay.com>) id 1UsG1e-0002Zs-AU
for bitcoin-development@lists.sourceforge.net;
Thu, 27 Jun 2013 17:30:30 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.47 as permitted sender)
client-ip=74.125.82.47; envelope-from=jgarzik@bitpay.com;
helo=mail-wg0-f47.google.com;
Received: from mail-wg0-f47.google.com ([74.125.82.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UsG1c-0002fs-BP
for bitcoin-development@lists.sourceforge.net;
Thu, 27 Jun 2013 17:30:30 +0000
Received: by mail-wg0-f47.google.com with SMTP id l18so798632wgh.2
for <bitcoin-development@lists.sourceforge.net>;
Thu, 27 Jun 2013 10:30:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:x-gm-message-state;
bh=Ev/KZORHvTGYO8cvlWgM7lvXiRGYl9YSGf9EHM7dKcU=;
b=VVtdOoDSzKwZT+uPGDAEm6RjayTbfuE1iOudlMfz5CHyS3KUuoSsd9o9W6ooaLBro5
QRf+0u9DNLsSvo5vMPRWj7EvaYQAvob1J2WyJPPnBQQiYZodscwgunLLX+flnTIe7BkU
ulfECxvWGUNXZ+sBUOliue210iVeoK7OmRK26ZQgViN8n9xS6qFNPmbZm8TlDaADQw1o
p8EI5UjfujocmLTaKnTB8s8SIldbKcaQGRbiME2b1zlDf101DZ3LmjmITzZrzFksjCCF
gzj/iFcJ/j96xeTleYvT5nhdkZNzGCKHbpRif9cEVZFSuhT7djnGiDuOGGJN0QTbE6Xu
NVjg==
MIME-Version: 1.0
X-Received: by 10.180.188.36 with SMTP id fx4mr13572355wic.55.1372354221975;
Thu, 27 Jun 2013 10:30:21 -0700 (PDT)
Received: by 10.194.178.69 with HTTP; Thu, 27 Jun 2013 10:30:21 -0700 (PDT)
In-Reply-To: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
Date: Thu, 27 Jun 2013 13:30:21 -0400
Message-ID: <CAJHLa0Ncac9Xt-AQBnpghqqpfR-j6Xtd9qVQoUe2dPp0kJvz1A@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Jim <jim618@fastmail.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkK+49Buagngd6oIz09ttku6uzp0odKVLBs7FqIlWCDpTbRSG+A9wvVvdG2P7kwL9DjWc8e
X-Spam-Score: -1.6 (-)
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 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UsG1c-0002fs-BP
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop
client on bitcoin.org
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: Thu, 27 Jun 2013 17:30:30 -0000
On Thu, Jun 27, 2013 at 1:10 PM, Jim <jim618@fastmail.co.uk> wrote:
> Hello Everybody,
>
> Over the last few months we have been steadily adding
> functionality to MultiBit including:
> + encrypted wallets
> + sign and verify message
> + stability improvements and bug fixes.
>
> As a result of these efforts I think MultiBit is now
> suitable for the entry level Bitcoin user. I propose
> that we put MultiBit as the default desktop client
> on the bitcoin.org "Choose your wallet" page.
>
> I think a typical new user comes to bitcoin.org from a
> google search or a Bitcoin news article. We want them to
> peruse the bitcoin.org site and try out a wallet. They
> should be able to get MultiBit up and running in a tea break.
> Then perhaps they get a colleague to send them some bitcoin
> from an Android phone by zapping a QR code.
This is definitely a great discussion to have. Here are some initial,
unprioritized thoughts. As an engineer, there is never a clear
answer, but a balance of costs and benefits.
Arguments in favor of moving away from Bitcoin-Qt/bitcoind for wallet services:
* Bitcoin-Qt is admittedly a very simple wallet. I see it's core
strengths more as a "P2P router" for the public blockchain data.
* Wallet feature innovation moves more slowly than
Armory/bitcoinj/blockchain.info.
* Requires the full blockchain, which is resource-intensive versus SPV.
Arguments in favor of retaining Bitcoin-Qt/bitcoind default:
* More field experience, code review and testing on desktop than others
* Very real possibility of an overall net reduction of full nodes on P2P network
Arguments in favor of multibit default:
* Good user interface, perhaps more friendly for entry level users as
you describe
* Based on bitcoinj, which has field experience and a very large
installed base thanks to Bitcoin Wallet/Schildbach
Arguments against multibit default:
* Less testing, field experience on desktop
I'm sure others can come up with a few more.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
