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
|
Return-Path: <kohli@ctemplar.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id EC21BC000D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Sep 2021 08:03:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id D73834013A
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Sep 2021 08:03:48 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level:
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5 tests=[BAYES_50=0.8,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=ctemplar.com
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id xnVjsnxplQeY
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Sep 2021 08:03:47 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from mail.ctemplar.com (mail.ctemplar.com [82.221.128.126])
by smtp4.osuosl.org (Postfix) with ESMTPS id 6D33A400FC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Sep 2021 08:03:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=ctemplar.com; s=ctemplar; h=Message-Id:References:In-Reply-To:Date:To:From:
Subject:Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Reply-To:
Cc:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:
List-Subscribe:List-Post:List-Owner:List-Archive;
bh=gkZKfsubDdMKYlb5bFt99bkHfqmQt7fNP7w30qG6fhI=; b=vgZ4S0e4XiyNLzGXL6aILkIkNl
GkBGUkeW9dc5OsHBvfnWRvSQh4mTdXfrp3GWWNNfHLV5F5TrLm8txE8aZ4hdJynvI9qlS9VMvPzGZ
cTBs7RKyjIRBUa9/ilHEmFJev35KkTC5rT9uhu1YA9H1jFgGS5IHZwTgF7lPBLQ+e5aw=;
Received: from ip6-localhost ([::1] helo=mail.ctemplar.com)
by mail.ctemplar.com with esmtp (envelope-from <kohli@ctemplar.com>)
id 1mPgwI-0003sh-Qz; Mon, 13 Sep 2021 08:03:43 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "pool2win" <kohli@ctemplar.com>
To: zmnscpxj@protonmail.com, bitcoin-dev@lists.linuxfoundation.org
Date: Mon, 13 Sep 2021 08:03:42 -0000
In-Reply-To: <CAO1K=nmhhMuisAXdddC1OSDUP2q8XsQjAUO4CVnyx8+BBvvwTw@mail.gmail.com>
References: <MiuahdA--3-2@tutanota.de>
<ceFmn7ZHyPHN70rDuE66lnPEwjgjQ7LtZLwyFgIVUpPvPDvSZSsLHUf_yiBvXTpjdEju4UxAOnDgilZaQAMvQzYcUbOkZsYvOIpuBG7japo=@protonmail.com>
<edbbb44e247d4e639659e1b9b989dd84-kohli@ctemplar.com>
<CAO1K=nnGXasdu_M4NgCkcCFMB16sW5r-Xd462d6jfR9mBBCgSA@mail.gmail.com>
<pqkX9ft1aIX7oRHcgAL2jxwO1VZlnSpWrwNiwhD0ru_-zH9LpQbc5008jmR3dg_z0q_k5zwCQPrhPryLRIYP7aUn8EvjpSeX7zfMztLsfzs=@protonmail.com>
<CAO1K=nmhhMuisAXdddC1OSDUP2q8XsQjAUO4CVnyx8+BBvvwTw@mail.gmail.com>
Message-Id: <06d43253aa86489989352c0dfa2bcf8e-kohli@ctemplar.com>
Feedback-ID: a29obGlAY3RlbXBsYXIuY29t:ctemplar
X-Mailman-Approved-At: Mon, 13 Sep 2021 08:07:40 +0000
Subject: Re: [bitcoin-dev] Braidpool: Proposal for a decentralised mining
pool
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: Mon, 13 Sep 2021 08:03:49 -0000
Hi Filippo,
If a malicious miner, M broadcasts {m1, m2 ... mn} at a regular interval, *and* also broadcasts {m1*, mn*} where mn* is bitcoin block then M will cheat all other miners of their reward. You correctly identified this attack. The problem stems from the fact that I wanted to use the bitcoin block as the sentinel to mark the shares from the DAG that need to be rewarded. There's a few approaches we can take here, but I think the best one is that the hub broadcasts a "sentinel" to mark out the point in logical time up to which shares will be rewarded.
m1* <-------------------- mn*<--------+
|
m1 <----m2 <---m3 <-------------------+
^ ^ ^ |
| | | |
| | +-----------+ |
| | | |
| +--------+ | SENTINEL
+-----+ | | |
| | | |
a1 <------ a2 <-----a3 <------+
In the above diagram, when hub receives mn*, the bitcoin block to be rewarded, the hub has also received {m1...m3, a1...a3} and therefore rewards all those shares and broadcasts this logical time to the p2p by sending a sentinel announcement.
This solution will also scale to the multiple hubs construction, as each hub will define their own sentinel and the miners working with each hub can independently verify their shares are being correctly rewarded. The solution also handles the case where M is not referencing any other shares.
The above alternative, might also answer your question about why we need to build a DAG. With a DAG we can capture logical time. Without a DAG, the above solution will require the hub to announce the hash of shares from each miner that have been rewarded.
I really appreciate you taking the time to go through the proposal and pointing out the attack. I hope the above solution addresses your concerns.
Thanks and best regards
pool2win
|
