summaryrefslogtreecommitdiff
path: root/77/d27881f98dae4d04e71f4bcf4dfbea5772eb07
blob: f2ce41a01a3c2e8057e5d24f8760e9805e3daa19 (plain)
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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
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 <mark@monetize.io>) id 1Tfxgk-0003TW-E5
	for bitcoin-development@lists.sourceforge.net;
	Tue, 04 Dec 2012 18:57:50 +0000
Received: from mail-qa0-f54.google.com ([209.85.216.54])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Tfxgg-0007vb-RE
	for bitcoin-development@lists.sourceforge.net;
	Tue, 04 Dec 2012 18:57:50 +0000
Received: by mail-qa0-f54.google.com with SMTP id j15so1178318qaq.13
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 04 Dec 2012 10:57:41 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type:x-gm-message-state;
	bh=1l1fs2yvAppUd6wTz7yNjoh0dwEr6di8KI2ORQYu29c=;
	b=ifb/qBzYBjUiunJVfVYYL3GgC3rKcfp96bt4ItLI8dRwH5Sd/P7DoCnTRc8DZolo7c
	Nl7FZCSH24etX+ZT+zY3b7be+MoYy1KOAYtWNV9ktRIOswrVxBJ1igQXbjKNz9msic85
	mg7dUMpX3UP0XJ9Aq5j4Ot4PqZ6Su7MYK4qguTszu3NQ2ACIsbvwUJuh3teW2lmFj+nR
	M7YBfeYbmopNEq4GbsiEb9HPRgjpAl1O7b5O6rMJby/NDGQkBCkiI5/PVeBNJUtCMvdv
	7Cu+ZRzg5SAvX37u0S99e9Q36WR0aQ6sDX9IXEByHutQumImiEtFYvEQZYkhZUk6w4zB
	loUw==
MIME-Version: 1.0
Received: by 10.224.201.73 with SMTP id ez9mr24260580qab.92.1354647461039;
	Tue, 04 Dec 2012 10:57:41 -0800 (PST)
Received: by 10.49.120.4 with HTTP; Tue, 4 Dec 2012 10:57:40 -0800 (PST)
X-Originating-IP: [128.102.238.175]
In-Reply-To: <CANEZrP3=GdyTe+2=cp-ROOJ8_t=yCqO-7GQ4hA-3aksg46p+ww@mail.gmail.com>
References: <CANEZrP3=GdyTe+2=cp-ROOJ8_t=yCqO-7GQ4hA-3aksg46p+ww@mail.gmail.com>
Date: Tue, 4 Dec 2012 10:57:40 -0800
Message-ID: <CACh7GpHUE2CYAMfRdAVPv1WAk102z94KYCWPV87fzzQEaP_hfw@mail.gmail.com>
From: Mark Friedenbach <mark@monetize.io>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=20cf3010edafb60e8d04d00b70f7
X-Gm-Message-State: ALoCoQlP6sn6lAn4OXwBt6Zy/tF1RrkmnBHWB5otb8ZSt95raLzZgC73KwTP1pfWQ/3i7FuH7KeY
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1Tfxgg-0007vb-RE
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Roadmap to getting users onto SPV clients
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: Tue, 04 Dec 2012 18:57:50 -0000

--20cf3010edafb60e8d04d00b70f7
Content-Type: text/plain; charset=UTF-8

Alan's UTxO meta-chain proposal becomes vastly easier to do now that
ultraprune is merged. That would allow the Satoshi client to know it's
wallet balance and operate with a >=SPV level of security during the
initial block download, and keep them on the path of becoming a full node.
If users can see their balances, send and receive transactions, and
otherwise go about their business (except for mining) during the initial
block download, would that not address your concerns?

IMHO the only time bitcoin.org should recommend a SPV-only client is when
it is dynamically when it is being accessed from a mobile device, but
that's a separate issue.

Mark


On Tue, Dec 4, 2012 at 9:46 AM, Mike Hearn <mike@plan99.net> wrote:

> At the moment if you visit bitcoin.org then you're recommended to
> download the full client. I think we all agree that at some point we
> need to start presenting users with something more like this:
>
>
> To get started, download wallet apps A or B.
>
> If you'd like to contribute your computing resources to the Bitcoin
> network and have a fast computer with an unfiltered internet
> connection, download:
>
>    - for desktop machines, Bitcoin-Qt
>    - for servers, bitcoind
>
>
>
> Obviously not that exact wording.
>
> I personally feel it's a bit early for this, but it's true that users
> are being turned away by the fact that they're pointed to Bitcoin-Qt
> by default, so having some kind of roadmap or plan for changing that
> would be good.
>
> I think MultiBit is maturing into a client that I'd feel comfortable
> recommending to end users who take the fast-start path, though it
> still has a few serious lacks (encrypted wallets aren't released yet,
> bloom filters will help performance a lot, needs to catch up with some
> newer features). But there doesn't have to be a one true client.
>
> The alternative, I guess, is to make Bitcoin-Qt have an SPV mode. I'm
> not convinced this is the best use of time, but if somebody steps up
> to do it, that could also work. MultiBit has some unique features that
> are quite useful like integrating charting and exchange rate feeds.
>
> What does everyone think on this?
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--20cf3010edafb60e8d04d00b70f7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Alan&#39;s UTxO meta-chain proposal becomes vastly easier to do now that ul=
traprune is merged. That would allow the Satoshi client to know it&#39;s wa=
llet balance and operate with a &gt;=3DSPV level of security during the ini=
tial block download, and keep them on the path of becoming a full node. If =
users can see their balances, send and receive transactions, and otherwise =
go about their business (except for mining) during the initial block downlo=
ad, would that not address your concerns?<br>
<br>IMHO the only time <a href=3D"http://bitcoin.org">bitcoin.org</a> shoul=
d recommend a SPV-only client is when it is dynamically when it is being ac=
cessed from a mobile device, but that&#39;s a separate issue.<br><br>Mark<b=
r>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Dec 4=
, 2012 at 9:46 AM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"mailto:mike@=
plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
At the moment if you visit <a href=3D"http://bitcoin.org" target=3D"_blank"=
>bitcoin.org</a> then you&#39;re recommended to<br>
download the full client. I think we all agree that at some point we<br>
need to start presenting users with something more like this:<br>
<br>
<br>
To get started, download wallet apps A or B.<br>
<br>
If you&#39;d like to contribute your computing resources to the Bitcoin<br>
network and have a fast computer with an unfiltered internet<br>
connection, download:<br>
<br>
=C2=A0 =C2=A0- for desktop machines, Bitcoin-Qt<br>
=C2=A0 =C2=A0- for servers, bitcoind<br>
<br>
<br>
<br>
Obviously not that exact wording.<br>
<br>
I personally feel it&#39;s a bit early for this, but it&#39;s true that use=
rs<br>
are being turned away by the fact that they&#39;re pointed to Bitcoin-Qt<br=
>
by default, so having some kind of roadmap or plan for changing that<br>
would be good.<br>
<br>
I think MultiBit is maturing into a client that I&#39;d feel comfortable<br=
>
recommending to end users who take the fast-start path, though it<br>
still has a few serious lacks (encrypted wallets aren&#39;t released yet,<b=
r>
bloom filters will help performance a lot, needs to catch up with some<br>
newer features). But there doesn&#39;t have to be a one true client.<br>
<br>
The alternative, I guess, is to make Bitcoin-Qt have an SPV mode. I&#39;m<b=
r>
not convinced this is the best use of time, but if somebody steps up<br>
to do it, that could also work. MultiBit has some unique features that<br>
are quite useful like integrating charting and exchange rate feeds.<br>
<br>
What does everyone think on this?<br>
<br>
---------------------------------------------------------------------------=
---<br>
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial<br>
Remotely access PCs and mobile devices and provide instant support<br>
Improve your efficiency, and focus on delivering more value-add services<br=
>
Discover what IT Professionals Know. Rescue delivers<br>
<a href=3D"http://p.sf.net/sfu/logmein_12329d2d" target=3D"_blank">http://p=
.sf.net/sfu/logmein_12329d2d</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>

--20cf3010edafb60e8d04d00b70f7--