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
|
Return-Path: <nta@nathanalexander.net>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
by lists.linuxfoundation.org (Postfix) with ESMTP id C167EC000D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Oct 2021 12:30:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id AFD8783AF1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Oct 2021 12:30:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7,
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: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=nathanalexander.net
header.b="Tk/GM8h4"; dkim=pass (2048-bit key)
header.d=messagingengine.com header.b="MU364Ml+"
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id qH6vuXk5dYhG
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Oct 2021 12:30:59 +0000 (UTC)
X-Greylist: delayed 00:07:47 by SQLgrey-1.8.0
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
[66.111.4.28])
by smtp1.osuosl.org (Postfix) with ESMTPS id 0434183AF0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Oct 2021 12:30:58 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
by mailout.nyi.internal (Postfix) with ESMTP id 766C15C0070
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Oct 2021 08:23:11 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
by compute4.internal (MEProxy); Tue, 05 Oct 2021 08:23:11 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
nathanalexander.net; h=to:from:subject:message-id:date
:mime-version:content-type:content-transfer-encoding; s=fm3; bh=
3JB/3Zx17sHH/cnQt5tslQArCLCmt88jMeZN0jNBD5A=; b=Tk/GM8h432tm9gnT
c/6N2WDp6qHhozNQn684s9O4K1JDIJJV5KhopdY5tQh6AUbAJ+UzuT817y9fGDau
ukTM2P8sGIsVlDK8t0ivv24mZqlXCUlfh3QmDWouLqE3jk29VajjxTb3272EPp3Y
c/k9sG5WRua2k+GzkH8JAflmdkLgGIkkgMiaC6CVsCizzPNaaTaCuhowYJhW0FLV
NXLNy3h106SEksILSEg8j3zfvsRz3abKfYa+viXAlui01p+S15+dABWwLdvkNB1l
XNxiC7yMGuMj3UvtLLQiOOfhjCmgKSicolgRksga6uOR9haU62DOA7CiXUD+28eq
S48FDA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=content-transfer-encoding:content-type
:date:from:message-id:mime-version:subject:to:x-me-proxy
:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=3JB/3Z
x17sHH/cnQt5tslQArCLCmt88jMeZN0jNBD5A=; b=MU364Ml+f+8ndypBXBRSq5
AG8my2W657xVrFzCpKUsE826Z44nwKzJvbjv2zfytxjeFLKDNscR3D/JHhfD8iWJ
ug/e/ZqFhTXb5K+ePWNhs/90DQxWzTBbzYWiIpz0fccb7C6PCSCXxhwT348growe
TQxthaZJtnZ3OtljEj/ipjnhv1oyKF57ZKlSpFIlDQBA5tjQnmd3n3xRhZDyIs0L
tiIDzBtKPdQ7JPRLRjmjn8t4ZeuJxFFXo35OtNa312RXlLHOyjN1aw3GrqvTM5Qb
Ai0Fxp+y+m+L6sUcjQwDeHgihVyCkgOvAjzQjXs0KxtBWTP6+GBQcv6jToE8LP4Q
==
X-ME-Sender: <xms:r0NcYYQf8TJliAPU-38RwUEq1mzJdRRU4NtRTL16k-n6uct9uU1CkA>
<xme:r0NcYVwfoSAIBZR44wMKw0hxlQRoxq6L7y7u6jph-Mpbba_1nN4cip3Jw1ZC4SBuY
7BXk8TUtb2gKvXe>
X-ME-Received: <xmr:r0NcYV1a904zectdIJdoVBa-Bkj7m_vTvUlf3IrUhZ8l6B-rQWfTBCCJM_-ALJg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudelgedgheduucetufdoteggodetrfdotf
fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
uceurghilhhouhhtmecufedttdenucenucfjughrpefvhffukffffgggtgfgsehtjeertd
dtfeejnecuhfhrohhmpefprghthhgrnhcuvfcutehlvgigrghnuggvrhcuoehnthgrsehn
rghthhgrnhgrlhgvgigrnhguvghrrdhnvghtqeenucggtffrrghtthgvrhhnpeehlefhge
egudduvddvieduuefgleehhfffudfgffehjeehueehfeegvdefleffgeenucevlhhushht
vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnthgrsehnrghthhgrnh
grlhgvgigrnhguvghrrdhnvght
X-ME-Proxy: <xmx:r0NcYcBzIBOXlCNg-7WYUw9z_JbLiImH3Wf-eSo6BUycjheEtl0PRQ>
<xmx:r0NcYRiNE75ISRv6qzBE4tIAtxV9EnG1CoWwtvg4e8IBJ37qcf1ksg>
<xmx:r0NcYYo_HeLDt6UZXrnrChXaBH3RwJyol1pqf0cWo23WAUxVa4EQYw>
<xmx:r0NcYbdhT2PRsNPvONtzN7Hat9FBRlcU67vr7zKih5rYmG9UUfIe_A>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for
<bitcoin-dev@lists.linuxfoundation.org>; Tue,
5 Oct 2021 08:23:10 -0400 (EDT)
To: bitcoin-dev@lists.linuxfoundation.org
From: Nathan T Alexander <nta@nathanalexander.net>
Message-ID: <f867f949-9a04-329b-ea1b-26201f46d2ab@nathanalexander.net>
Date: Tue, 5 Oct 2021 07:23:09 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.13.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Mailman-Approved-At: Tue, 05 Oct 2021 14:09:36 +0000
Subject: [bitcoin-dev] Question- must every mining rig attempt every block?
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: Tue, 05 Oct 2021 12:30:59 -0000
For purposes of conserving energy, couldn't each mining rig have some
non-gameable attribute which would be used to calculate if a block would
be accepted by that rig?
Don't the mining rigs have to be able to identify themselves to the
network somehow, in order to claim their block reward? Could their
bitcoin network ID be used as a non-gameable attribute?
Essentially a green light / red light system. In order for a block to be
accepted by the network, it must have all attributes of a successful
block today, and it must also have come from a rig that had a green light.
Perhaps hash some data from the last successful block, along with the
miners non-gameable attribute, and if it's below a certain number set by
algorithm, the miner gets a green light to race to produce a valid block.
Nathan Alexander
Arlington, TX
|
