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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
|
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 4320F279
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 5 Aug 2015 22:14:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com
[209.85.213.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5F7B4274
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 5 Aug 2015 22:14:08 +0000 (UTC)
Received: by igbij6 with SMTP id ij6so104463592igb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 05 Aug 2015 15:14:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=e/Fhp6ODxX3F0v0JhWQ9ylF0hEx7YuSyNes5TGxDp1M=;
b=YXQQEuCHEQ1hwRhusaZxm2s+r9luxDoKg5cqN4k7uOV9GJGyMmk13YNAL5/7YHbONs
pEiw/yy/ErwAKVAREK4MzpqqL4RitzPEsdh+V/xBKat6VwOnPIwGl8aGKRdIrkFFxxh/
f/jem0AjQc7h1mQQoQm2sLuQ1+cm4dPsAOFV0ru/IOKzLYnXBtI52G8vdi4CWyJUOe2Q
3x0d1puID4mJVhlTQ1OFBAynWUWsB/kJU3+fp08oD6B8E3oe8gpIWtOXpNhAv7rAw72T
kcDIPzBnG6MyKoKl70A+VSpLlEvM2+6Qf64VS+C/J+6WIMwuL2WL7upHfEnOrgLPSvL6
yZxA==
MIME-Version: 1.0
X-Received: by 10.50.126.42 with SMTP id mv10mr246263igb.66.1438812847716;
Wed, 05 Aug 2015 15:14:07 -0700 (PDT)
Received: by 10.107.14.136 with HTTP; Wed, 5 Aug 2015 15:14:07 -0700 (PDT)
In-Reply-To: <CALwsPgm9S3UNd3bEuWreyGS7bcvSD+cXxueoD+F_D9fC=xLz2Q@mail.gmail.com>
References: <CALwsPgnnkbfUBhL=Qyspz13pnZ-6RHdaZOGvfLG34JjJRgt2Dw@mail.gmail.com>
<B3546CB9-6A24-474C-8B56-9B1E2D33B470@mattcorallo.com>
<CALwsPgm6xcBfLXZTNTZ40R_s3oUawE0ANZycDWpSo0cXZ+=-Vg@mail.gmail.com>
<CAAS2fgQLNH+rivNNTFz6xt_9SxO3fFj7-3z7A-_B_2X2x-6M5w@mail.gmail.com>
<CALwsPgm9S3UNd3bEuWreyGS7bcvSD+cXxueoD+F_D9fC=xLz2Q@mail.gmail.com>
Date: Wed, 5 Aug 2015 22:14:07 +0000
Message-ID: <CAAS2fgSXWzCv=4cF=0bwL9+udzBHSPR7goL3U_c1NjS22dpWzQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Arnoud Kouwenhoven - Pukaki Corp <arnoud@pukaki.bz>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, 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
Cc: Arnoud Kouwenhoven - Pukaki Corp via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Idea: Efficient bitcoin block propagation
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 05 Aug 2015 22:14:09 -0000
On Wed, Aug 5, 2015 at 9:19 PM, Arnoud Kouwenhoven - Pukaki Corp
<arnoud@pukaki.bz> wrote:
> Thanks for this (direct) feedback. It would make sense that if blocks can be
> submitted using ~5kb packets, that no further optimizations would be needed
> at this point. I will look into the relay network transmission protocol to
> understand how it works!
>
> I hear that you are saying that this network solves speed of transmission
> and thereby (technical) block size issues. Presumably it would solve speed
> of block validation too by prevalidating transactions.
Correct. Bitcoin Core has cached validation for many years now... if
not for that and other optimizations, things would be really broken
right now. :)
> Assuming this is all
> true, and I have no reason to doubt that at this point, I do not understand
> why there is any discussion at all about the (technical) impact of large
> blocks, why there are large numbers of miners building on invalid blocks
> (SPV mining, https://bitcoin.org/en/alert/2015-07-04-spv-mining), or why
> there is any discussion about the speed of block validation (cpu processing
> time to verify blocks and transactions in blocks being a limitation).
I'm also mystified by a lot of the large block discussion, much of it
is completely divorced from the technology as deployed; much less what
we-- in industry-- know to be possible. I don't blame you or anyone in
particular on this; it's a new area and we don't yet know what we need
to know to know what we need to know; or to the extent that we do it
hasn't had time to get effectively communicated.
The technical/security implications of larger blocks are related to
other things than propagation time, if you assume people are using the
available efficient relay protocol (or better).
SPV mining is a bit of a misnomer (If I coined the term, I'm sorry).
What these parties are actually doing is blinding mining on top of
other pools' stratum work. You can think of it as sub-pooling with
hopping onto whatever pool has the highest block (I'll call it VFSSP
in this post-- validation free stratum subpooling). It's very easy to
implement, and there are other considerations.
It was initially deployed at a time when a single pool in Europe has
amassed more than half of the hashrate. This pool had propagation
problems and a very high orphan rate, it may have (perhaps
unintentionally) been performing a selfish mining attack; mining off
their stratum work was an easy fix which massively cut down the orphan
rates for anyone who did it. This was before the relay network
protocol existed (the fact that all the hashpower was consolidating on
a single pool was a major motivation for creating it).
VFSSP also cuts through a number of practical issues miners have had:
Miners that run their own bitcoin nodes in far away colocation
(>100ms) due to local bandwidth or connectivity issues (censored
internet); relay network hubs not being anywhere near by due to
strange internet routing (e.g. japan to china going via the US for ...
reasons...); the CreateNewBlock() function being very slow and
unoptimized, etc. There are many other things like this-- and VFSSP
avoids them causing delays even when you don't understand them or know
about them. So even when they're easily fixed the VFSSP is a more
general workaround.
Mining operations are also usually operated in a largely fire and
forget manner. There is a long history in (esp pooled) mining where
someone sets up an operation and then hardly maintains it after the
fact... so some of the use of VFSSP appears to just be inertia-- we
have better solutions now, but they they work to deploy and changing
things involves risk (which is heightened by a lack of good
monitoring-- participants learn they are too latent by observing
orphaned blocks at a cost of 25 BTC each).
One of the frustrating things about incentives in this space is that
bad outcomes are possible even when they're not necessary. E.g. if a
miner can lower their orphan rate by deploying a new protocol (or
simply fixing some faulty hardware in their infrastructure, like
Bitcoin nodes running on cheap VPSes with remote storage) OR they can
lower their orphan rate by pointing their hashpower at a free
centeralized pool, they're likely to do the latter because it takes
less effort.
|
