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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 5F81EC0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 13:35:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 39AFF402E1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 13:35:29 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level:
X-Spam-Status: No, score=-1.599 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, FREEMAIL_FROM=0.001,
FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_NONE=-0.0001,
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: smtp2.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=protonmail.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 ANYiLRmlyoHs
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 13:35:27 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch
[185.70.40.137])
by smtp2.osuosl.org (Postfix) with ESMTPS id C01B94027F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 13:35:27 +0000 (UTC)
Date: Sun, 23 May 2021 13:35:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail; t=1621776924;
bh=RWltppEu4iyG8WwldahIFVr+CMQREat6Bomd/jZj8Uo=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From;
b=XW+rHZ4I48Qwjbw6qf2UZjA8Tz/PEGzPjktBsvUWBQordiAmu+VwNWAcP7mZnnwGQ
9VgGLgV+qJd/7ViagwVasrAmXs62K4oydkKyMIyqwbFpw7rdfIJT/PldCoY6VMEDXP
Aw2TgHVJD+Ewdqw8GWGE9cNmULBJYVK37ZF8o32c=
To: Karl <gmkarl@gmail.com>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <G3RgofdarOhSiEJjyDNaN2Dv27WCpb_0CSOpya6acUnPbpPQ-oygklpP_e0rLdxglK5FCo5dq7Qkv6GinA3qCXiOM6GzEcNvcxxM7kbwFhY=@protonmail.com>
In-Reply-To: <CALL-=e7hHYm96KJEFEiTgEaSjK0VTcNcGypLVekmaxYNN+egEA@mail.gmail.com>
References: <CANQHGB1N4E9=cqrkxDiUH5hAHgzURAJv+S7Vkf8xWEMJ=+T_AQ@mail.gmail.com>
<KVDgWlVOrIW9ahW8jA8W1eSK-w0OzVEjx585MpJiNL-SuX9x-td_VzNEtFSDNj-bwulh_nLExtNBl4WD6x2Ipjp9bQvT4Jo3NIqoyDxoBBM=@protonmail.com>
<CALL-=e7hHYm96KJEFEiTgEaSjK0VTcNcGypLVekmaxYNN+egEA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reducing block reward via soft fork
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, 23 May 2021 13:35:29 -0000
Good morning Karl,
> On 5/23/21, ZmnSCPxj via bitcoin-dev
> bitcoin-dev@lists.linuxfoundation.org wrote:
>
> > Good morning James,
> >
> > > Background
> > >
> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > >
> > > Reducing the block reward reduces the incentive to mine. It reduces t=
he
> > > maximum energy price at which mining is profitable, reducing the ener=
gy
> > > use.
> >
> > If people want to retain previous levels of security, they can offer to=
pay
> > higher fees, which increases the miner reward and thereby increasing th=
e
> > energy use again.
>
> The turn-around time for that takes a population of both users and
> miners to cause. Increasing popularity of bitcoin has a far bigger
> impact here, and it is already raising fees and energy use at an
> established rate.
>
> If it becomes an issue, as bandwidth increases block size could be
> raised to lower fees.
>
Which increases block rewards somewhat (at least to some level that matches=
the overall security of the network) and you still have the same amount of=
energy consumed.
> > Properly account for the entropy increase (energy usage) of all kinds o=
f
> > pollution, and the free market will naturally seek sustainable and rene=
wable
> > processes --- because that maximizes profitability in the long run.
>
> There is little economic incentive to fine carbon emissions because
> there is no well-established quick path to gain profit from reducing
> them. The feedback paths you describe take decades if not hundreds of
> years.
>
> But it sounds like you are saying you would rather the energy issue
> stay a political one that does not involve bitcoin. Your point is
> quite relevant because bitcoin is not the largest consumer of energy;
> those who care about reducing energy use would be better put to look
> at other concerns.
Precisely.
> > What is needed is to enforce that pollution be paid for by those who ca=
use
> > it --- this can require significant political influence to do (a major =
world
> > government is a major polluter, willing to pay for high fuel costs just=
to
> > ship their soldiers globally, polluting the environments of foreign
> > countries), and should be what true environmentalists would work toward=
s,
> > not rejecting Bitcoin as an environmental disaster (which is frankly
> > laughable).
> > Remember, the free market only works correctly if all its costs are
> > accounted correctly --- otherwise it will treat costs subsidized by the
> > community of human beings as a resource to pump.
>
> It sounds like you would prefer a proof-of-work function that directly
> proved carbon offsetting? And an on-chain tax for environmental harm?
The problem is that the only proof of efficiency here is implicit: any inef=
ficiency will eventually be rooted out of the network, as any inefficiency =
will translate to reduced profitability.
However, at short-term, a miner can pollute its locality, and then exit the=
business and leave its crap lying around for others to deal with and absco=
nd with pure profit.
This translates to a theft in the profitability of others in the locality.
How to prove this is not happening?
The best you can do is to have some number of authorities sign off on wheth=
er or not they are doing this.
The problem is that authorities are bribeable.
Alternately, other entities in the locality can use force to require the po=
lluting entity to clean up or suffer significant consequences.
This at least is better incentive-wise, as they others in the same locality=
are the ones most affected, but the ability to enforce may be difficult du=
e to various political constructions; the miners could be in such deep caho=
ots with the local government that the local government would willingly hur=
t other local entities in the vicinity of the polluting entity.
Regards,
ZmnSCPxj
|
