Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TfwZo-0001vA-Bs for bitcoin-development@lists.sourceforge.net; Tue, 04 Dec 2012 17:46:36 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.47 as permitted sender) client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f47.google.com; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TfwZm-0005cq-Kk for bitcoin-development@lists.sourceforge.net; Tue, 04 Dec 2012 17:46:36 +0000 Received: by mail-oa0-f47.google.com with SMTP id h1so4460300oag.34 for ; Tue, 04 Dec 2012 09:46:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.13.198 with SMTP id j6mr12100064oec.51.1354643189276; Tue, 04 Dec 2012 09:46:29 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.128.139 with HTTP; Tue, 4 Dec 2012 09:46:29 -0800 (PST) Date: Tue, 4 Dec 2012 18:46:29 +0100 X-Google-Sender-Auth: 24SoiU7eZw0aJrQwD6Irmiyzbmw Message-ID: From: Mike Hearn To: Bitcoin Dev Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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: 1TfwZm-0005cq-Kk Subject: [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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2012 17:46:36 -0000 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?