summaryrefslogtreecommitdiff
path: root/aa/2571451e18ca058c30f1132903c116a48b94da
blob: 66fa8a176b1e3cca0585039e3d2f715f9994f927 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
Return-Path: <gmaxwell@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 991807AA
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Aug 2016 08:34:24 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ua0-f193.google.com (mail-ua0-f193.google.com
	[209.85.217.193])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9228A1E6
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Aug 2016 08:34:22 +0000 (UTC)
Received: by mail-ua0-f193.google.com with SMTP id u13so792512uau.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Aug 2016 01:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to:cc:content-transfer-encoding;
	bh=FhJ1J4qPKjimofyH055RYdhkVnnFOleqVemYvt3szLY=;
	b=M9jyESzCidui9NQuJmnXyUZmC02iWE5jFGFAhID1hYoXblYsQoecU2e5XzydUlS2va
	B5e2Ot9eD3L9Jqxmjnbt0Sh8mbNTK7lPa7E4b6756ma9W5wHGv4OW/VRW2CO8Y8iwOzc
	9mt99S9Ss8aftFLhX4y8runNP2F/EmNmZ+wrRAVG15uXMeOgtLFNl6tJii+ctFDQoLg7
	PytvHU0va2HpD1YH4VeZp8KdBh0TCc1wzO74nMnsyK0zmN5k7RYgiyLJsx09G7Gc9r9w
	bbwR2yRweP+77DdGx24d4Q//j7w7Xtc0aAxV/7t8IeZ26exDewp+2xwF0qcZTgG/Y9Az
	TQSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
	:date:message-id:subject:to:cc:content-transfer-encoding;
	bh=FhJ1J4qPKjimofyH055RYdhkVnnFOleqVemYvt3szLY=;
	b=OOoLFAhhVmaDItHBMUK/N67Akczmel2buRlZe5Jg7FmUITjUTwkwJNwIXGqix8iAGG
	RMoYeMfS/NFKyXZRjkwn7H2nWnGNMQk6y2pbe7lG8ayaQA/RSs91AIVsDLKeVXKpFu7M
	LrpZBKKwOb8TVp0od27Q7fYxfvS6K65mBhLe1cY7YbMcjgRfrScMEfNQ7KewpjgaMnfY
	qBF+qmwf8yI7cmop2v0wNlLrt2WrpmnzwaDJ+luUgm/FIA05b/ljggjUZKdDG7Eg4/0S
	8mUWePylaxS27U1Xiq3A/Na20qiUlozMnWblbu4vMQAgLwY1u6OCcFHhYultLMbjZ/nX
	MRyg==
X-Gm-Message-State: AEkoousX9q748QSMd0us3RPjQr86l++CGUVtcB1tQ4fB8PW9Z0LjHBOxVH2jRtmXejfUA/tmstZNKXP6WySTUw==
X-Received: by 10.31.98.133 with SMTP id w127mr1019187vkb.29.1472027661555;
	Wed, 24 Aug 2016 01:34:21 -0700 (PDT)
MIME-Version: 1.0
Sender: gmaxwell@gmail.com
Received: by 10.103.118.69 with HTTP; Wed, 24 Aug 2016 01:34:20 -0700 (PDT)
In-Reply-To: <7FF3E128-4D92-46CC-8FBA-9B9E9A9FC7AD@keepkey.com>
References: <201608232012.12588.luke@dashjr.org>
	<7FF3E128-4D92-46CC-8FBA-9B9E9A9FC7AD@keepkey.com>
From: Gregory Maxwell <greg@xiph.org>
Date: Wed, 24 Aug 2016 08:34:20 +0000
X-Google-Sender-Auth: VuGjfQjwNydu-t4rXrkh2PA6fqY
Message-ID: <CAAS2fgSm_5hnP854ygp50FKQnH_5K239b+1E3Zw=ANTU6pe5Sw@mail.gmail.com>
To: Kenneth Heutmaker <ken@keepkey.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.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
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 08:34:24 -0000

On Tue, Aug 23, 2016 at 8:54 PM, Kenneth Heutmaker via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> SPV is kinda broken if the wallet doesn=E2=80=99t do this detection. If y=
our wallet connects only to nodes that don=E2=80=99t support bloom filterin=
g, the wallet never gets updates. We have had a spike in users reporting th=
at their wallet isn't getting updated. To compound the problem, they rescan=
 the blockchain and lose all of their transaction history. It has caused mu=
ch panic among less technical users.
>
> We believe that failing to detect the NODE_BLOOM bit is the culprit, alth=
ough it is non-deterministic, so we aren't certain.

There are almost no NODE_BLOOM supporting bloom-off nodes on the
network currently. So, while supporting this is important, I am
doubtful that its the current problem you've suffered.

There are a great many fake nodes which appear to exist purely to
monitor transactions. Many do not implement enough of the protocol to
support scanning or transaction relay. (and, in fact, relaying
transactions would make monitoring less effective).

You can't count on peers on a peer to peer network to be honest and
cooperative. Implementations need to work hard to be robust to abusive
peers. Unfortunately, the design of the bloom filtering is such that
it isn't always easy (or even possible) to be robust.