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
|
Return-Path: <jlrubin@mit.edu>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 83715C0012
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Dec 2021 16:43:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 62DA740227
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Dec 2021 16:43:28 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id XFHRGfy_MXGR
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Dec 2021 16:43:27 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by smtp2.osuosl.org (Postfix) with ESMTPS id 2532D400CE
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Dec 2021 16:43:26 +0000 (UTC)
Received: from mail-lf1-f46.google.com (mail-lf1-f46.google.com
[209.85.167.46]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1BCGhOmB007172
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Sun, 12 Dec 2021 11:43:25 -0500
Received: by mail-lf1-f46.google.com with SMTP id t26so26812866lfk.9
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Dec 2021 08:43:25 -0800 (PST)
X-Gm-Message-State: AOAM533fGsJSVZDqdk3FYWgaLGYWsn+BsJiOzurbKlWYpvLrTU1Mh7Zp
TKe4mJWODez4VwFrorAH2CblH3TdJC9jzGZ972g=
X-Google-Smtp-Source: ABdhPJxewg7BRnb1w+Iz0083HtM3FMNTwL4oBJyES9TS1Rt68xvvVddWUCER0e9YiUVYeU/s7Ey8oSfLKyUpfXzvm/A=
X-Received: by 2002:ac2:5615:: with SMTP id v21mr25617219lfd.112.1639327403734;
Sun, 12 Dec 2021 08:43:23 -0800 (PST)
MIME-Version: 1.0
From: Jeremy <jlrubin@mit.edu>
Date: Sun, 12 Dec 2021 08:43:12 -0800
X-Gmail-Original-Message-ID: <CAD5xwhgOK6p7fqZPha1jvDgo=4Syti9K46a2A48Eas44dn9v6Q@mail.gmail.com>
Message-ID: <CAD5xwhgOK6p7fqZPha1jvDgo=4Syti9K46a2A48Eas44dn9v6Q@mail.gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000091faa105d2f5a79e"
Subject: [bitcoin-dev] [Bitcoin Advent Calendar] Decentralized Coordination
Free Mining Pools
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sun, 12 Dec 2021 16:43:28 -0000
--00000000000091faa105d2f5a79e
Content-Type: text/plain; charset="UTF-8"
Howdy, welcome to day 15!
Today's post covers a form of a mining pool that can be operated as sort of
a map-reduce over blocks without any "infrastructure".
https://rubin.io/bitcoin/2021/12/12/advent-15/
There's still some really open-ended questions (perhaps for y'all to
consider) around how to select an analyze the choice of window and payout
functions, but something like this could alleviate a lot of the
centralization pressures typically faced by pools.
Notably, compared to previous attempts, combining the payment pool payout
with this concept means that there is practically very little on-chain
overhead from this approach as the chain-load
for including payouts in every block is deferred for future cooperation
among miners. Although that can be considered cooperation itself, if you
think of it like a pipeline, the cooperation happens out of band from
mining and block production so it really is coordination free to mine.
Cheers,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
--00000000000091faa105d2f5a79e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:#000000">Howdy, welcome to day 15!=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif;font-size:small;color:#000000"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#0=
00000">Today's post covers a form of a mining pool that can be operated=
as sort of a map-reduce over blocks without any "infrastructure"=
.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sa=
ns-serif;font-size:small;color:#000000"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#=
000000"><a href=3D"https://rubin.io/bitcoin/2021/12/12/advent-15/">https://=
rubin.io/bitcoin/2021/12/12/advent-15/</a><br></div><div><br></div><div><di=
v class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;f=
ont-size:small;color:rgb(0,0,0)">There's still some really open-ended q=
uestions (perhaps for y'all to consider) around how to select an analyz=
e the choice of window and payout functions, but something like this could =
alleviate a lot of the centralization pressures typically faced by pools.</=
div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-=
serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:r=
gb(0,0,0)">Notably, compared to previous attempts, combining the payment po=
ol payout with this concept means that there is practically very little on-=
chain overhead from this approach as the chain-load</div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;=
color:rgb(0,0,0)">for including payouts in every block is deferred for futu=
re cooperation among miners. Although that can be considered cooperation it=
self, if you think of it like a pipeline, the cooperation happens out of ba=
nd from mining and block production so it really is coordination free to mi=
ne.</div><br></div><div><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">Cheer=
s,</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;col=
or:rgb(0,0,0)">Jeremy</div><br clear=3D"all"><div><div dir=3D"ltr" class=3D=
"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">--<br=
><a href=3D"https://twitter.com/JeremyRubin" target=3D"_blank">@JeremyRubin=
</a><a href=3D"https://twitter.com/JeremyRubin" target=3D"_blank"></a></div=
></div></div></div>
--00000000000091faa105d2f5a79e--
|
