Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.181 as permitted sender)
	client-ip=209.85.212.181; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f181.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CANEZrP2WiCm+oQGJppWLGGVWsgaFg3mwtEEwcrXc+-Sy+K0V+Q@mail.gmail.com>
References: <CAAS2fgTVp7PhdJMfz-huyOsp=6Ca9wH6cVkedMgntXnK+ZpDXg@mail.gmail.com>
	<CAAS2fgQWpkJZ26qx6_2ECVg3qGFw7H5Nx9L0ow0bboD6PWV4Lg@mail.gmail.com>
	<CANEZrP2WiCm+oQGJppWLGGVWsgaFg3mwtEEwcrXc+-Sy+K0V+Q@mail.gmail.com>
Date: Fri, 16 Nov 2012 18:44:32 +0100
Message-ID: <CANEZrP3R8rCotBDfOYJ68Wicg11a999QAi=hmTrZ3HLzvvs3-w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6db2ee605e5e704cea0521f
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum security model concerns
Precedence: list

--0016e6db2ee605e5e704cea0521f
Content-Type: text/plain; charset=UTF-8

BTW have you checked the code? I took a quick look and didn't see things I
was expecting to see. In particular I couldn't find any code that manages
wallet state in the presence of re-orgs. It appears to check that
transactions appeared in the block chain, but if there's a chain switch
it's not clear to me the wallet will be in the right state.

I saw a message from Thomas on his thread saying something like "can't
spend coins bug happens when there's a re-org and the server gives you the
wrong histories, to fix it reset your wallet and switch to a new server"
.... which to me rather implies there's no re-org handling at all.

If Electrum does end up doing all SPV work correctly, how is it different
to MultiBit? Just the deterministic wallet seeding?


On Fri, Nov 16, 2012 at 4:59 PM, Mike Hearn <mike@plan99.net> wrote:

> Great to hear that.

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

BTW have you checked the code? I took a quick look and didn&#39;t see thing=
s I was expecting to see. In particular I couldn&#39;t find any code that m=
anages wallet state in the presence of re-orgs. It appears to check that tr=
ansactions appeared in the block chain, but if there&#39;s a chain switch i=
t&#39;s not clear to me the wallet will be in the right state.<div>
<br></div><div>I saw a message from Thomas on his thread saying something l=
ike &quot;can&#39;t spend coins bug happens when there&#39;s a re-org and t=
he server gives you the wrong histories, to fix it reset your wallet and sw=
itch to a new server&quot; .... which to me rather implies there&#39;s no r=
e-org handling at all.</div>
<div><br></div><div>If Electrum does end up doing all SPV work correctly, h=
ow is it different to MultiBit? Just the deterministic wallet seeding?</div=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Nov =
16, 2012 at 4:59 PM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"mailto:mik=
e@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Great to hear that.
</blockquote></div><br></div>

--0016e6db2ee605e5e704cea0521f--