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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 6207942B
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 03:26:59 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail3.protonmail.ch (mail3.protonmail.ch [185.70.40.25])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5CEC7477
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 03:26:58 +0000 (UTC)
Date: Mon, 12 Feb 2018 22:26:47 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=default; t=1518492415;
bh=wOdA4Ha/wNhfgVYRq6kXFLDjEgrI1I47Nmka26JPoUE=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:
Feedback-ID:From;
b=t6bC3c/bQyuEmZHEbyPLqx7W7SDGFW0E/gxqYoTaxcLMcgNmPHwwszGr1GcRnAwhb
JwoA2DOq6194hjH+9tOpun/C9dPS08gvyTNcIyYJoR2qBksJIRfGr8GrEH/ta1y9j8
kzQMs2bXz/4erIBYn4NLEZZJJlqFJciA0IaMIp5w=
To: Helder Garcia <helder.garcia@gmail.com>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <x1rOm5WuZPrKyBLCBpEvK756G1XwBP0m4xnNbVSEwEI0kRqmgfikXUylnpR0Qnsn9Ek6IQ97dvcBZNWuq7b17CsfEpa1SYtDDnN4sHEMsYw=@protonmail.com>
In-Reply-To: <6EAA8D06-3A20-4BBA-BE2E-95B42BCCE7D3@gmail.com>
References: <6EAA8D06-3A20-4BBA-BE2E-95B42BCCE7D3@gmail.com>
Feedback-ID: el4j0RWPRERue64lIQeq9Y2FP-mdB86tFqjmrJyEPR9VAtMovPEo9tvgA0CrTsSHJeeyPXqnoAu6DN-R04uJUg==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, FROM_LOCAL_NOVOWEL,
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
X-Mailman-Approved-At: Tue, 13 Feb 2018 03:29:37 +0000
Cc: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP0008 clarification
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: Tue, 13 Feb 2018 03:26:59 -0000
Good morning Helder,
>Hi,
>
> I=E2=80=99m trying to understand the process of signalling and activation=
of updates in bitcoin. Following BIP34, BIP9, I got into BIP8.
> In my understanding of what I read there, an update will be activated eve=
n if the threshold of 95% signalling is not reached in STARTED state, as so=
on as blockchain height is equal or higher than timeout_height.
> Is my understanding correct? If so, isn=E2=80=99t it a risk to activate a=
change even if you don=E2=80=99t have the majority of hash power accepting=
it?
Assuming the update is widespread among economic actors, only miners who do=
not follow the more stringent rules of the update will suffer, as their bl=
ocks will have a high probability of not following those rules and thus wil=
l be implicitly rejected by economic actors. Rational miners who follow th=
e update, no matter how small their hash power share, would prefer the chai=
n that economic actors will accept as real and would build only on blocks t=
hat follow updated rules strictly.
Indeed, the time from STARTED to ACTIVE simply serves to let miners upgrade=
their software, as a concession that in the real world we cannot safely de=
ploy new software in a single day.
Regards,
ZmnSCPxj
|
