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
|
Return-Path: <john.tromp@gmail.com>
Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 24415C0051
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Sep 2020 17:24:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by hemlock.osuosl.org (Postfix) with ESMTP id 0CEA98757E
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Sep 2020 17:24:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from hemlock.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id U-jC+BSJHoIV
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Sep 2020 17:24:00 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-wr1-f43.google.com (mail-wr1-f43.google.com
[209.85.221.43])
by hemlock.osuosl.org (Postfix) with ESMTPS id A89AA87578
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Sep 2020 17:23:59 +0000 (UTC)
Received: by mail-wr1-f43.google.com with SMTP id s12so4443720wrw.11
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 25 Sep 2020 10:23:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=YdBvhyYNSxU24u+dfl4vBvRF0soK2dMhpJ1qF62Bfo4=;
b=oBUgPL+lmbAqJ/96ERZW1b28aapRALpUglUa2q8hJnJwLtynVy9wUuLL1bQUbBB28l
yAgg+sPgWGvFx17halHxlKoXjfhQIq2KrjlWGp8asW/sHb3tBW42Z2NgRBIbh7U5etde
b+hdnrM9i953FDRsh2Oa11r51WaITjwPb9UC46XIr9o4oOb5PQq3FDpiPZXA6BJ+dczD
D+awUcIFdHZfVQvPXjunAgHrLSd9ZRHMEOdcAe6NeMrDr0CCaYYYNF63dr10oe+1KbO7
XQRd2nNkwqaDaqS5Sd/+I94gmQIe9f5eAOXrn805YtcPbQ3vuRaeo01++qMMrNnT4KJU
HG+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=YdBvhyYNSxU24u+dfl4vBvRF0soK2dMhpJ1qF62Bfo4=;
b=DiJJJFZEfARU6/F0/wwKLGluCcQIJHapzd/IRsGm3JNZRE3PeqiKCrt5Nf2PFNjUqG
k7p6KMBg5utAzjDozZ6CwRSMt08UpYUJtpUgnRIQ+NnHogjUH4Q+7WTZIq7v5sDKeih+
z0iDtMI8dbPG3gEchdTatgqZbFQhR5TgkkBs739kPrCK54oS8V9XXb4pUQ3ql8K0szkb
JoKzGxRi2XF1uiCwtS8JXsPThlOAJeOX415h0NTftBuFBa1cNkMcCD20TJOHqBApN73l
m8BQap8M5rykeTz5Dd/YXTwCvnWLL4oxF4IDdLWk7nt+VdfcIbxh9nDIFTZm7PC+C6a0
qAFA==
X-Gm-Message-State: AOAM53141wPCzZ18cmFBCyHgvrkupe5dixzQUoo6MMulGgSEpg2v7ZQ6
vlk2DGjQUa47ktFxOlecAwityE5IizBcSnM3igzG+knnM/1f
X-Google-Smtp-Source: ABdhPJwPUhjXMi5EY4J7yVDYfT8AYwzvyCrPX05lEO/FlhUpOXVYj8HglSuUytL1BOPEfYRMNop/ETVovxVk3sOZN3A=
X-Received: by 2002:adf:c3cc:: with SMTP id d12mr5684955wrg.399.1601054637716;
Fri, 25 Sep 2020 10:23:57 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.27861.1601049417.32591.bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <mailman.27861.1601049417.32591.bitcoin-dev@lists.linuxfoundation.org>
From: John Tromp <john.tromp@gmail.com>
Date: Fri, 25 Sep 2020 19:23:46 +0200
Message-ID: <CAOU__fxsxwakwJP6NtxVM+67U2SRj77LYKormcSO+_hmy9sG8A@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailman-Approved-At: Fri, 25 Sep 2020 17:52:18 +0000
Subject: Re: [bitcoin-dev] Floating-Point Nakamoto Consensus (bitcoin ml)
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: Fri, 25 Sep 2020 17:24:01 -0000
Re: Floating-Point Nakamoto Consensus (bitcoin ml)
>
> This is a pretty big departure from cumulative POW.
It's still cumulative. But instead of cumulating network difficulty,
they cumulate log_2(solution difficulty).
So if two solutions are found simultaneously, and one has a hash
that's only half of the other, then that will have twice the solution
difficulty and thus contribute 1 more the cumulate log_2(solution
difficulty).
> Could you explain to me what you see happening if a node with this patch
> and no history starts to sync, and some random node gives it a block
> with a better fitness test for say height 250,000? No other solution
> will have a better fitness test at that height, so from my understanding
> its going to stop syncing. How about even later - say this proposal is
> activated at block 750,000. At 850,000, someone decides it'd be fun to
> publish a new block 800,000 with a better fitness test. What happens the
> 50,000 blocks?
Nothing happens in these cases, as the new blocks are still far behind
the tip in cumulative score (they just have higher score at their
height).
regards,
-John
|
