Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <robbak@robbak.com>) id 1TgD7V-0005f5-H1
	for bitcoin-development@lists.sourceforge.net;
	Wed, 05 Dec 2012 11:26:29 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of robbak.com
	designates 74.125.82.43 as permitted sender)
	client-ip=74.125.82.43; envelope-from=robbak@robbak.com;
	helo=mail-wg0-f43.google.com; 
Received: from mail-wg0-f43.google.com ([74.125.82.43])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1TgD7R-0006Rf-A7
	for bitcoin-development@lists.sourceforge.net;
	Wed, 05 Dec 2012 11:26:29 +0000
Received: by mail-wg0-f43.google.com with SMTP id e12so2413503wge.10
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 05 Dec 2012 03:26:19 -0800 (PST)
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
	:content-type:x-gm-message-state;
	bh=Uxb3dKXRlJJqKe5LQt3/2qs1ViG7L2IOUZmttdmEBGU=;
	b=IUYsU7Yoy6JdNd18euOGR+htZwJUW/q8IIDW7vEtzV2pQ3D7VfMJPDmxcXdmr/1VAL
	WvnZQUyBtL82YDszAl0Uh1cRR9xlpq3Li3VKyRx2UQJtr1eQmQzMTH0bqUA/knRn8SLB
	Zn6hhmqmNJ0H6OzSOnAdG6vDBpdsSdcgnQ24/vSu9G1WLlvNIuGLAWmH/RlC7OFXY4K/
	mZBAXjApUGTmvAb8SUn6AgWJpce4cLi9WEu8DO0ZQS0UHhobRzZpRT+a88UaxHwzn5mT
	TBVke9TTUwt4PrTp4s2yHAxPb8sYCKCACjNTcdTm09Plm9w0xwBAzYhXk8Ij4NwiP0Ga
	WKHg==
MIME-Version: 1.0
Received: by 10.180.108.38 with SMTP id hh6mr2280619wib.0.1354702756620; Wed,
	05 Dec 2012 02:19:16 -0800 (PST)
Received: by 10.194.71.109 with HTTP; Wed, 5 Dec 2012 02:19:16 -0800 (PST)
In-Reply-To: <CAKm8k+2nWgKbEL+iWp7-rmMXYJNsxWz6E9SFy8AMtWiRoead7g@mail.gmail.com>
References: <CANEZrP3=GdyTe+2=cp-ROOJ8_t=yCqO-7GQ4hA-3aksg46p+ww@mail.gmail.com>
	<CAAS2fgQYV7aR86QOwvqMLpFZ+MAwSOSZvV6XuZdXvqjeYziRng@mail.gmail.com>
	<CANEZrP3ZhNYrgQZT4qOohejs3yhgt0c_kT5zwAUVtPP1Q9f1Zg@mail.gmail.com>
	<CAAS2fgSJhX4974BdWGdyJA13kHg7mTgHadC6UdhdUPu0bDDXFg@mail.gmail.com>
	<CALf2ePw82wt08_G2RtUYEBxorjY1ryZ4r+W7atSzDLYMU+rGGQ@mail.gmail.com>
	<CAAS2fgQewysOG7eOHQxmLup4oLJK=jY=q-_4qTL6yKQ855g3ew@mail.gmail.com>
	<50BEACAB.3070304@gmail.com>
	<CAAS2fgRfUMYwOE51+eY5QE8nDNV==G1OBRzM1AuHjYmYwTFiow@mail.gmail.com>
	<CAGjxm7vFkunziwECv1Twq4M9eC0nbgcqdCK6t6i7R84R_kPUTA@mail.gmail.com>
	<CA+s+GJByVMpHLdOnnAiaBYNUACRi7CFr6=NX+Ocg7R6zktQUSA@mail.gmail.com>
	<CAKm8k+2nWgKbEL+iWp7-rmMXYJNsxWz6E9SFy8AMtWiRoead7g@mail.gmail.com>
Date: Wed, 5 Dec 2012 20:19:16 +1000
Message-ID: <CA+i0-i8JqW-wX6gMhJTjmbNfW9me1BifS635dnFrHT1A8KRpig@mail.gmail.com>
From: Robert Backhaus <robbak@robbak.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=e89a8f3ba5c195a94104d0185030
X-Gm-Message-State: ALoCoQktaez6vOgTXpOgJ1x79HyaTYU7YViv3So9Jr/wSdfvk0m0wYuMq4i4S4gdrocP7DnVXejP
X-Spam-Score: -0.5 (/)
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
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1TgD7R-0006Rf-A7
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: Wed, 05 Dec 2012 11:26:29 -0000

--e89a8f3ba5c195a94104d0185030
Content-Type: text/plain; charset=ISO-8859-1

On 5 December 2012 19:43, Gary Rowe <g.rowe@froot.co.uk> wrote:

> I would like to chime on on the user experience of the SPV client (in
> particular MultiBit).
>
> Without exception, everyone that I have introduced Bitcoin (which is a lot
> of people) have expected an "instant-on" experience. It has to clobber
> PayPal and credit cards or people won't give it a second look, let alone a
> second chance. SPV clients deliver on that expectation.
>
> Once the user has the great initial "wow!" moment then their interest in
> Bitcoin is reinforced and they tend to explore further, particularly into
> the economic theory behind it. Many decide to install the full node out of
> a sense of community contribution to the security of the network.
>
> Having a hybrid mode of SPV first then full node second should be
> something that a user has control over - it is their computing resources we
> are using after all and Bitcoin should not be perceived as a drain.


Hybrid SPV sounds like a good idea to me. Allows it to work out-of-the-box,
then slowly gets up-to-speed with the full network - working low priority,
or even not at all, if it detects a slow system or network link.
Another idea is always distributing the client with a checkpoint that is
only days old, then starting by pulling in more recent blocks, so it can
transact. Following that, it will pull in progressively older blocks as
time permits.

--e89a8f3ba5c195a94104d0185030
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><div class=3D"gmail_quote">On 5 December 2012 19=
:43, Gary Rowe <span dir=3D"ltr">&lt;<a href=3D"mailto:g.rowe@froot.co.uk" =
target=3D"_blank">g.rowe@froot.co.uk</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
I would like to chime on on the user experience of the SPV client (in parti=
cular MultiBit). <br><br>Without exception, everyone that I have introduced=
 Bitcoin (which is a lot of people) have expected an &quot;instant-on&quot;=
 experience. It has to clobber PayPal and credit cards or people won&#39;t =
give it a second look, let alone a second chance. SPV clients deliver on th=
at expectation. <br>

<br>Once the user has the great initial &quot;wow!&quot; moment then their =
interest in Bitcoin is reinforced and they tend to explore further, particu=
larly into the economic theory behind it. Many decide to install the full n=
ode out of a sense of community contribution to the security of the network=
.<br>

<br>Having a hybrid mode of SPV first then full node second should be somet=
hing that a user has control over - it is their computing resources we are =
using after all and Bitcoin should not be perceived as a drain.</blockquote=
>
<div><br>Hybrid SPV sounds like a good idea to me. Allows it to work out-of=
-the-box, then slowly gets up-to-speed with the full network - working low =
priority, or even not at all, if it detects a slow system or network link. =
<br>
Another idea is always distributing the client with a checkpoint that is on=
ly days old, then starting by pulling in more recent blocks, so it can tran=
sact. Following that, it will pull in progressively older blocks as time pe=
rmits.<br>
</div></div></div>

--e89a8f3ba5c195a94104d0185030--