From: Kenneth Heutmaker <ken@keepkey•com>
To: Luke Dashjr <luke@dashjr•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Status updates (including to Active/Final Status) - BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130
Date: Tue, 23 Aug 2016 13:54:50 -0700 [thread overview]
Message-ID: <7FF3E128-4D92-46CC-8FBA-9B9E9A9FC7AD@keepkey.com> (raw)
In-Reply-To: <201608232012.12588.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
> Additionally, BIP 111 (NODE_BLOOM service bit) has been implemented in Bitcoin
> Core and derivatives; it is unclear if used by clients yet. Can developers of
> such clients please comment and let me know: 1) if their software supports
> this BIP already; 2) if not, do they intend to support it in the future?
> If and only if there are any clients using this service bit already, I will
> update BIP 111 to Final Status in 2 weeks also.
Multibit is adding detection of the NODE_BLOOM bit in the next 2-3 weeks.
SPV is kinda broken if the wallet doesn’t do this detection. If your wallet connects only to nodes that don’t support bloom filtering, the wallet never gets updates. We have had a spike in users reporting that their wallet isn't getting updated. To compound the problem, they rescan the blockchain and lose all of their transaction history. It has caused much panic among less technical users.
We believe that failing to detect the NODE_BLOOM bit is the culprit, although it is non-deterministic, so we aren't certain.
I imagine that other SPV wallets are having similar issues. BIP 111 really isn’t optional at this point, so it should be marked final.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-08-23 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 20:12 Luke Dashjr
2016-08-23 20:54 ` Kenneth Heutmaker [this message]
2016-08-24 6:59 ` Jonas Schnelli
2016-08-24 8:34 ` Gregory Maxwell
2016-08-24 12:51 ` Thomas Voegtlin
2016-08-24 13:47 ` Andreas Schildbach
2016-08-24 18:22 ` Luke Dashjr
2016-08-24 14:18 ` Jonas Schnelli
2016-08-24 14:42 ` Jochen Hoenicke
2016-08-25 7:39 ` Jonas Schnelli
2016-08-25 7:56 ` Thomas Voegtlin
2016-08-25 8:08 ` Jonas Schnelli
2016-08-25 8:12 ` Jonas Schnelli
2016-08-25 8:50 ` Marek Palatinus
2016-08-25 9:02 ` Pieter Wuille
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=7FF3E128-4D92-46CC-8FBA-9B9E9A9FC7AD@keepkey.com \
--to=ken@keepkey$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/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