summaryrefslogtreecommitdiff
path: root/ef/749443c6ced1d328e87a39ccb0b0a358bf5c73
blob: a4d1d0431275fd0172fd9049c2cae7f17fea2e92 (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
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
Return-Path: <eric@voskuil.org>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id A6496C000E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 30 Jun 2021 09:17:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 84154403AA
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 30 Jun 2021 09:17:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=voskuil-org.20150623.gappssmtp.com
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 l-wo4H6gNXPg
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 30 Jun 2021 09:17:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com
 [IPv6:2607:f8b0:4864:20::62e])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 5412440137
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 30 Jun 2021 09:17:09 +0000 (UTC)
Received: by mail-pl1-x62e.google.com with SMTP id b1so1108029pls.5
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 30 Jun 2021 02:17:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=voskuil-org.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:references:in-reply-to:subject:date:message-id
 :mime-version:thread-index:content-language;
 bh=0ixi8VhIeXmgQGLlccnxWMU1tDJuodTqYUy4VvSDHvU=;
 b=V7qwbsPaAADOZ+H5//07t8wKNv1RN+Ri7lHYTHS/tjYPlb8lp+biyAvLX0hhxeOM5q
 6c0TuT+7NZsD0OwyWPDXirvfJhaSsgU6IEErFBegyBs12YtXAg5XNNKbwHLyrwkHkGLt
 4aSvrwO3cBkpPoDGiv/6qDzNfrEU435PDgHFbvSsBBGOkaD4nvpo9PPTuRiuXIuETlIu
 Z/DY7keVDU26NTBA4c+tD4z+l+1AL9ojlOwr3/VUOWswDDX1vJiyANxuefzgTPSu9m5p
 IarOQ8NNUs3nzwnXXS0140prT45Br2j6sQ1CkmBLaPz7g8vx8eOIc5lvHVwT+NgAGOlu
 +BjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date
 :message-id:mime-version:thread-index:content-language;
 bh=0ixi8VhIeXmgQGLlccnxWMU1tDJuodTqYUy4VvSDHvU=;
 b=uKjuj7lUFBoFWUbyGoeZaPyVwiEvMolCci3VKs7N/meue8CWZazFX21s66iBFMPR8h
 nmnE3lTKjNDxP3M8C55PqDOTlqRnaBNWsnvqBS5epy0MQs4GbeqGrVmR7S6ei+BDCN37
 13BJLxQosoMvVOHI+bjwgmXsTrsIqBybm8mcaS1ElHLnlAH711j/LmyHLSzj8Nv1v16e
 T0Tou7KgXHR9Y5GFYKKxQMCns2CJSyQBg53FugjSxYQb+7p3Y1AsQ+zEbRuZYg9paBBt
 xV5arLG4NcZBe7Tp4bL40vHCrgnaLF30evM5PRp36n0bVgpxpJlGOHj8Kryg8KhS/v0x
 3NIw==
X-Gm-Message-State: AOAM530XwxX0Wtl554IJVQ716HuVSlw6LoQr+hBSS5T4Ago5tjHGmB3j
 KjNFVX1dMRS1Pddn7zGW1vZ7iIOyka7ggW1W
X-Google-Smtp-Source: ABdhPJwEsMwylbgEjg35T6Re3Q3ZAQSwn4Y50QWae+6VkHuEHaYo/yjQU9dmI6vU9GvwB1cK+L07Jw==
X-Received: by 2002:a17:90b:3756:: with SMTP id
 ne22mr3572106pjb.197.1625044628546; 
 Wed, 30 Jun 2021 02:17:08 -0700 (PDT)
Received: from ERICDESKTOP ([2601:600:9c00:1d0::9d25])
 by smtp.gmail.com with ESMTPSA id d13sm6177748pjr.49.2021.06.30.02.17.08
 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 30 Jun 2021 02:17:08 -0700 (PDT)
From: <eric@voskuil.org>
To: "'Prayank'" <prayank@tutanota.de>
References: <MdCL7jI--3-2@tutanota.de>
In-Reply-To: <MdCL7jI--3-2@tutanota.de>
Date: Wed, 30 Jun 2021 02:17:08 -0700
Message-ID: <026701d76d90$b4095e30$1c1c1a90$@voskuil.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0268_01D76D56.07AC5AF0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQN841F/5R39lyQc4p184su8UE1c+KfhVP1Q
Content-Language: en-us
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: Wed, 30 Jun 2021 09:17:10 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0268_01D76D56.07AC5AF0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Prayank,

=20

> So majority hash power not following the consensus rules can result in =
chain split?

=20

Any two people on different rules implies a chain split. That=E2=80=99s =
presumably why rule changes are called forks. There is no actual concept =
of =E2=80=9Cthe rules=E2=80=9D just one set of rules or another.

=20

> Why would majority of miners decide to mine a chain that nobody wants =
to use?

=20

I don=E2=80=99t presume to know why people prefer one thing over =
another, or what people want to use, nor does economics.

=20

> What are different things possible in this case based on game theory?

=20

I=E2=80=99ve seen no actual demonstration of the relevance of game =
theory to Bitcoin. People throw the words around quite a bit, but I =
can=E2=80=99t give you an answer because I have found no evidence of a =
valid game theoretic model applicable to Bitcoin. It=E2=80=99s not a =
game, it=E2=80=99s a market.

=20

> Do miners and mining pools participate in discussions before signaling =
for a soft fork begins?

=20

Who knows, I don=E2=80=99t get invited to round table meetings.

=20

> Can they still mine something else post activation even if signaling =
readiness for soft fork?=20

=20

A person can mine whatever they want. Signaling does not compel a miner =
to enforce. Each block mined is anonymous. But each miner seeing the =
signals of others, unless they are coordinating, would presumably assume =
that others will enforce.

=20

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

=20

A node (software) doesn=E2=80=99t enforce anything. Merchants enforce =
consensus rules when they reject trading for something that they =
don=E2=80=99t consider money. Every time two people trade both party =
validates what they receive (not what they trade away). Those receiving =
Bitcoin are economically relevant and their power is a function of how =
much they are doing so.

=20

Miners censor, which is inconsequential unless enforced. Majority miners =
can enforce censorship by simply not building on any non-censoring =
blocks. This is what soft fork enforcement is.

=20

> Is soft fork signaling same as voting?

=20

I don=E2=80=99t see that it needs a label apart from signaling. There =
are many kinds of voting. It would be hard to equate signaling with any =
of them. It=E2=80=99s a public signal that the miner who mined a given =
block miner intends to censor, that=E2=80=99s all.

=20

> According to my understanding, miners follow the consensus rules =
enforced by full nodes and get (subsidy + fees) for their work.

=20

Miners mine a chain, which ever one they want. There are many. They earn =
the block reward.

=20

> Signaling is not voting although lot of people consider it voting =
including some mining pools and exchanges.

=20

What people consider it is inconsequential. It has clearly defined =
behavior.

=20

e

=20

From: Prayank <prayank@tutanota.de>=20
Sent: Sunday, June 27, 2021 5:01 AM
To: eric@voskuil.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Trinary Version Signaling for softfork

=20

Hello Eric,

=20

I have few questions:

=20

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

=20

So majority hash power not following the consensus rules can result in =
chain 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?=20

=20

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

=20

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?=20

=20

> 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 soft fork. =
It=E2=80=99s time Bitcoiners stop thinking of miners as other people. =
Anyone can mine, and that=E2=80=99s your vote.

=20

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

=20

Is soft fork signaling same as voting?

=20

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

=20

=20

--=20

Prayank


------=_NextPart_000_0268_01D76D56.07AC5AF0
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US =
link=3D"#0563C1" vlink=3D"#954F72" style=3D'word-wrap:break-word'><div =
class=3DWordSection1><p class=3DMsoNormal>Hi Prayank,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; So =
majority hash power not following the consensus rules can result in =
chain split?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Any two people on different rules implies a chain =
split. That=E2=80=99s presumably why rule changes are called forks. =
There is no actual concept of =E2=80=9Cthe rules=E2=80=9D just one set =
of rules or another.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; Why =
would majority of miners decide to mine a chain that nobody wants to =
use?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>I don=E2=80=99t presume to know why people prefer one =
thing over another, or what people want to use, nor does =
economics.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&gt; What are different things possible in this case =
based on game theory?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I=E2=80=99ve =
seen no actual demonstration of the relevance of game theory to Bitcoin. =
People throw the words around quite a bit, but I can=E2=80=99t give you =
an answer because I have found no evidence of a valid game theoretic =
model applicable to Bitcoin. It=E2=80=99s not a game, it=E2=80=99s a =
market.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&gt; Do miners and mining pools participate in =
discussions before signaling for a soft fork begins?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Who knows, I =
don=E2=80=99t get invited to round table meetings.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; Can =
they still mine something else post activation even if signaling =
readiness for soft fork?&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>A person can =
mine whatever they want. Signaling does not compel a miner to enforce. =
Each block mined is anonymous. But each miner seeing the signals of =
others, unless they are coordinating, would presumably assume that =
others will enforce.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; Who =
enforces consensus rules technically in Bitcoin? Full nodes or =
Miners?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>A node (software) doesn=E2=80=99t enforce anything. =
Merchants enforce consensus rules when they reject trading for something =
that they don=E2=80=99t consider money. Every time two people trade both =
party validates what they receive (not what they trade away). Those =
receiving Bitcoin are economically relevant and their power is a =
function of how much they are doing so.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Miners =
censor, which is inconsequential unless enforced. Majority miners can =
enforce censorship by simply not building on any non-censoring blocks. =
This is what soft fork enforcement is.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; Is soft =
fork signaling same as voting?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I =
don=E2=80=99t see that it needs a label apart from signaling. There are =
many kinds of voting. It would be hard to equate signaling with any of =
them. It=E2=80=99s a public signal that the miner who mined a given =
block miner intends to censor, that=E2=80=99s all.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; =
According to my understanding, miners follow the consensus rules =
enforced by full nodes and get (subsidy + fees) for their =
work.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Miners mine a chain, which ever one they want. There =
are many. They earn the block reward.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt; =
Signaling is not voting although lot of people consider it voting =
including some mining pools and exchanges.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>What people =
consider it is inconsequential. It has clearly defined =
behavior.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>e<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> Prayank =
&lt;prayank@tutanota.de&gt; <br><b>Sent:</b> Sunday, June 27, 2021 5:01 =
AM<br><b>To:</b> eric@voskuil.org<br><b>Cc:</b> Bitcoin Dev =
&lt;bitcoin-dev@lists.linuxfoundation.org&gt;<br><b>Subject:</b> Re: =
[bitcoin-dev] Trinary Version Signaling for =
softfork<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hello =
Eric,<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
have few questions:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>&gt;&nbsp;Without majority hash power support, =
activation simply means you are off on a chain split. =
<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>So majority hash power not following the consensus =
rules can result in chain 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;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>&gt;&nbsp;And activation without majority hash power =
certainly does not =E2=80=9Censure=E2=80=9D =
this.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>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;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>&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 =
soft fork. It=E2=80=99s time Bitcoiners stop thinking of miners as other =
people. Anyone can mine, and that=E2=80=99s your =
vote.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Who enforces consensus rules technically in Bitcoin? =
Full nodes or Miners?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Is soft fork signaling same as =
voting?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>According to my understanding, miners follow the =
consensus rules enforced by full nodes and get (subsidy + fees) for =
their work. Signaling is not voting although lot of people consider it =
voting including some mining pools and =
exchanges.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>-- <o:p></o:p></p></div><div><p =
class=3DMsoNormal>Prayank<o:p></o:p></p></div></div></body></html>
------=_NextPart_000_0268_01D76D56.07AC5AF0--