summaryrefslogtreecommitdiff
path: root/9f/aba4658908df29cd1ce6e07c69abfcfcc9750e
blob: 7aeeabd79ee576e8312481cf932e5c661f57dd62 (plain)
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
142
143
144
145
146
147
148
149
Return-Path: <prayank@tutanota.de>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id D2E89C000E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 27 Jun 2021 12:01:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id C1150402CA
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 27 Jun 2021 12:01:31 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level: 
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5
 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,
 RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
 SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=tutanota.de
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 WYPFo3Rop1QL
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 27 Jun 2021 12:01:29 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 947D7402C9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 27 Jun 2021 12:01:29 +0000 (UTC)
Received: from w3.tutanota.de (unknown [192.168.1.164])
 by w1.tutanota.de (Postfix) with ESMTP id A1A69FBF551;
 Sun, 27 Jun 2021 12:01:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1624795287; 
 s=s1; d=tutanota.de;
 h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender;
 bh=f7310v29kP68cyDDIqBorFdNrbfOOUkT8AFfvuXPe+4=;
 b=pkW4MNBjKyPSWJKuuK6mVAh1gltLRr+PBfCy+hrWTHe2RNm4CnWQ68S9DgZADzSd
 0MNFIlOF5hu1Xn1ZnJMg5lFds41Oo/OConTjMT9vkCCxiHynx1iQ06b9LXfwihk2cMy
 K07VVpQ57EfJc9tNNLwfIaLz07cSxMu37f/bBWndJYLFeHRvMs6kvZCBHrvxhKxPzEM
 wGdIBf6sDAb4wO3AooIWoCrdj+3gJvS1GlqPpPoQ0ZFOA5CQ0SxS26pXvbG0XbZ9eGp
 K/GCns0pMvdbzzmrjuBnuAua7lNccBwrEKO2InJNt8toKqddx46jxx5KrXSLF67FnVx
 whQl4cjD1A==
Date: Sun, 27 Jun 2021 14:01:27 +0200 (CEST)
From: Prayank <prayank@tutanota.de>
To: eric@voskuil.org
Message-ID: <MdCL7jI--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="----=_Part_465974_536232075.1624795287645"
X-Mailman-Approved-At: Sun, 27 Jun 2021 12:19:38 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Trinary Version Signaling for softfork
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, 27 Jun 2021 12:01:31 -0000

------=_Part_465974_536232075.1624795287645
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Eric,
I have few questions:

>=C2=A0Without majority hash power support, activation simply means you are=
 off on a chain split.=20

So majority hash power not following the consensus rules can result in chai=
n split? Why would majority of miners decide to mine a chain that nobody wa=
nts to use? What are different things possible in this case based on game t=
heory?=C2=A0

>=C2=A0And activation without majority hash power certainly does not =E2=80=
=9Censure=E2=80=9D this.

Do miners and mining pools participate in discussions before signaling for =
a soft fork begins? Can they still mine something else post activation even=
 if signaling readiness for soft fork?=C2=A0

>=C2=A0If one wants to enforce a soft fork (or otherwise censor) this is ac=
complished by mining (or paying others to do so). Anyone can mine, so every=
one gets a say. Mining is trading capital now for more later. If enough peo=
ple want to do that, they can enforce a soft fork. It=E2=80=99s time Bitcoi=
ners stop thinking of miners as other people. Anyone can mine, and that=E2=
=80=99s your vote.

Who enforces consensus rules technically in Bitcoin? Full nodes or Miners?

Is soft fork signaling same as voting?

According to my understanding, miners follow the consensus rules enforced b=
y full nodes and get (subsidy + fees) for their work. Signaling is not voti=
ng although lot of people consider it voting including some mining pools an=
d exchanges.


--=20
 Prayank
------=_Part_465974_536232075.1624795287645
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
">
  </head>
  <body>
<div>Hello Eric,</div><div dir=3D"auto"><br></div><div dir=3D"auto">I have =
few questions:<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">&gt;&=
nbsp;Without majority hash power support, activation simply means you are o=
ff on a chain split. <br></div><div dir=3D"auto"><br></div><div dir=3D"auto=
">So majority hash power not following the consensus rules can result in ch=
ain split? Why would majority of miners decide to mine a chain that nobody =
wants to use? What are different things possible in this case based on game=
 theory?&nbsp;<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">&gt;&=
nbsp;And activation without majority hash power certainly does not =E2=80=
=9Censure=E2=80=9D this.<br></div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">Do miners and mining pools participate in discussions before signaling=
 for a soft fork begins? Can they still mine something else post activation=
 even if signaling readiness for soft fork?&nbsp;<br></div><div dir=3D"auto=
"><br></div><div dir=3D"auto">&gt;&nbsp;If one wants to enforce a soft fork=
 (or otherwise censor) this is accomplished by mining (or paying others to =
do so). Anyone can mine, so everyone gets a say. Mining is trading capital =
now for more later. If enough people want to do that, they can enforce a so=
ft fork. It=E2=80=99s time Bitcoiners stop thinking of miners as other peop=
le. Anyone can mine, and that=E2=80=99s your vote.<br></div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Who enforces consensus rules technically in =
Bitcoin? Full nodes or Miners?<br></div><div dir=3D"auto"><br></div><div di=
r=3D"auto">Is soft fork signaling same as voting?<br></div><div dir=3D"auto=
"><br></div><div dir=3D"auto">According to my understanding, miners follow =
the consensus rules enforced by full nodes and get (subsidy + fees) for the=
ir work. Signaling is not voting although lot of people consider it voting =
including some mining pools and exchanges.<br></div><div dir=3D"auto"><br><=
/div><div><br></div><div>-- <br></div><div> Prayank</div>  </body>
</html>

------=_Part_465974_536232075.1624795287645--