From: Mike Hearn <mike@plan99•net>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum security model concerns
Date: Fri, 16 Nov 2012 18:44:32 +0100 [thread overview]
Message-ID: <CANEZrP3R8rCotBDfOYJ68Wicg11a999QAi=hmTrZ3HLzvvs3-w@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2WiCm+oQGJppWLGGVWsgaFg3mwtEEwcrXc+-Sy+K0V+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1218 bytes --]
prev parent reply other threads:[~2012-11-16 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 16:37 Gregory Maxwell
2012-10-08 11:52 ` Mike Hearn
2012-10-09 3:22 ` Gregory Maxwell
2012-10-10 11:19 ` Mike Hearn
2012-10-10 14:06 ` Gary Rowe
2012-10-10 15:23 ` Gregory Maxwell
2012-10-10 15:55 ` Mike Hearn
2012-11-15 23:45 ` Gregory Maxwell
2012-11-16 15:59 ` Mike Hearn
2012-11-16 17:44 ` Mike Hearn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP3R8rCotBDfOYJ68Wicg11a999QAi=hmTrZ3HLzvvs3-w@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox