Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.178 as permitted sender)
	client-ip=209.85.217.178; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f178.google.com; 
MIME-Version: 1.0
In-Reply-To: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
Date: Thu, 27 Jun 2013 10:56:54 -0700
Message-ID: <CAAS2fgTka6Dw94V0-vHBHxG=zadu9EmhKmfVm7Y_dQUUgrTf6w@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Jim <jim618@fastmail.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop
 client on bitcoin.org
Precedence: list

On Thu, Jun 27, 2013 at 10:10 AM, Jim <jim618@fastmail.co.uk> wrote:
> Let me know if you think this is a good idea (or not!)
> and if you have any questions.

Being able to promote a fast SPV desktop wallet would be great!

I went through an cycle of testing on multibit after I saw some
complaints when it went up on the page before without at lot of
discussion. There were a number of issues with it at the time, in
particular the frequent deadlocks=E2=80=94 though Mike was saying that thos=
e
should be fixed.

I see some of the the other things that were concerning for me at the
time are still uncorrected though, e.g. no proxy support (so users
can't follow our recommended best practices of using it with Tor),
that it reuses addresses (esp for change), that it doesn't clearly
distinguish confirmation level. It also make repeated https
connections to 141.101.113.245? (I'm not seeing the IP in the source,
and it doesn't have a useful reverse dns entry, so I can't tell what
its for).  Is there any timeframe for changing any of this stuff?