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 1UsUhV-0006R8-8o for bitcoin-development@lists.sourceforge.net; Fri, 28 Jun 2013 09:10:41 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.45 as permitted sender) client-ip=209.85.219.45; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f45.google.com; Received: from mail-oa0-f45.google.com ([209.85.219.45]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UsUhR-0006Ki-Hw for bitcoin-development@lists.sourceforge.net; Fri, 28 Jun 2013 09:10:40 +0000 Received: by mail-oa0-f45.google.com with SMTP id j1so2034116oag.32 for ; Fri, 28 Jun 2013 02:10:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.71.38 with SMTP id r6mr592756obu.64.1372410632155; Fri, 28 Jun 2013 02:10:32 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.23.36 with HTTP; Fri, 28 Jun 2013 02:10:32 -0700 (PDT) In-Reply-To: References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com> Date: Fri, 28 Jun 2013 11:10:32 +0200 X-Google-Sender-Auth: 8uZs4b3kG4X2s2Goy6kPwdv9A4I Message-ID: From: Mike Hearn To: Jeff Garzik 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: 1UsUhR-0006Ki-Hw Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 09:10:41 -0000 > Arguments in favor of retaining Bitcoin-Qt/bitcoind default: > * More field experience, code review and testing on desktop than others I'm hoping that if we start promoting alternative wallets their dev communities will get larger. Most bitcoinj code is peer reviewed, but not to the same extent that Bitcoin-Qt is. We're obviously not going to stop promoting Bitcoin-Qt as well. I think the distinction should be: * Want to get started fast? Grab MultiBit and you'll be under way in a couple of minutes. * Want to help out the Bitcoin network? Leave your computer switched on all the time and run Bitcoin-Qt instead. It will donate some of your computers resources to running the Bitcoin system. The MultiBit interface is OK but all desktop wallets could use some love from a friendly UI designer.