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
|
Return-Path: <rgrant@rgrant.org>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 99625C0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Mar 2021 13:42:51 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 727B66F4D0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Mar 2021 13:42:51 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level:
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5
tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001,
RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001]
autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id K6ewVFdyPWV6
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Mar 2021 13:42:50 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-wr1-f52.google.com (mail-wr1-f52.google.com
[209.85.221.52])
by smtp3.osuosl.org (Postfix) with ESMTPS id 2D8CD6F480
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Mar 2021 13:42:49 +0000 (UTC)
Received: by mail-wr1-f52.google.com with SMTP id u14so2153219wri.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 05 Mar 2021 05:42:49 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=WivnTA2AUFOAM4yUOMFIou8hh/ADAXzctBuODhLBb/E=;
b=REIWp1RPXs2hBRkWFCUlrFqlax2fgR9rlsk/jGmxMwZ2bvcd1UodzDGTBinJMFIJaB
LwbG8Fc1yd1EoN3hvzdQptVvXLC+rUL7pkStuwABfqCjUdFBd4lZEzefiGyXSxOVYMD3
zbRduPXSU1FQ4vqhFQwJwuqEksOwr3Kqb2LlyDLgKmi8eWNSs3G1At5KdSQfdRUDkCq+
CTEhil3x8/h9NDFLZVg7imrldSzHnGTlshl7TKbmS32KgNl9vRVTiDx5r0y4shWkTq36
aBk/62FP4TM9Yf8xMb5dzFFf56n5zSp/7NDiB4Bq4Xf4Qls+0NCjPM48yOEyV67hGJq6
uOiw==
X-Gm-Message-State: AOAM5307l35J7alYAL1yLuoqXR4FQqyF+DpKoV/i2CseCNrA1Xm+YhSu
XrNV8zb7ljB9qiMQltj8TF6XGkxLy9fa8v5gHcWhZA==
X-Google-Smtp-Source: ABdhPJwTL5cq2utBmPG9iKhLYABWWKVKiVbIk+yBQnc1oVZOkz0k3uWQE9cs2k8YO2XGeMxNQqCVu0NSOSjsnvf9F28=
X-Received: by 2002:adf:b313:: with SMTP id j19mr9272643wrd.188.1614951768232;
Fri, 05 Mar 2021 05:42:48 -0800 (PST)
MIME-Version: 1.0
References: <CA+YkXXxUdZFYTa1c-F=-FzoQQVtV3GUmE2Okec-zRAD3xS1qAQ@mail.gmail.com>
In-Reply-To: <CA+YkXXxUdZFYTa1c-F=-FzoQQVtV3GUmE2Okec-zRAD3xS1qAQ@mail.gmail.com>
From: Ryan Grant <bitcoin-dev@rgrant.org>
Date: Fri, 5 Mar 2021 13:42:22 +0000
Message-ID: <CAMnpzfop8ttqjMAKoS37zpQV6WiZfi1Bn+y_e-HaepTiD4Vm1Q@mail.gmail.com>
To: Lonero Foundation <loneroassociation@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST
Datastore for Energy Efficient Mining
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: Fri, 05 Mar 2021 13:42:51 -0000
On Fri, Mar 5, 2021 at 9:39 AM Lonero Foundation via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello, I want to start a new BIP proposal aiming to tackle some of
> the energy efficiency issues w/ Bitcoin mining. Excuse my ignorance
> given this is my first time making a BIP proposal, but is there a
> specific format I need to follow?
Hi Andrew,
I would like to discourage you from writing a BIP on this topic, as
any such proposal is guaranteed to be rejected based on prior
discussions in the community.
Please update your priors with the following:
https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki
BIP: 2
Title: BIP process, revised
https://www.truthcoin.info/blog/pow-cheapest/
"Nothing is Cheaper than Proof of Work"
on | 04 Aug 2015
Your topic brings up an interesting edge case, which is whether the
BIP repository is an open forum for all possible arguments that are
technically well constructed. Obviously: no; but by what
non-arbitrary process do we decide?
I propose that the BIP Editor's role should include preserving signal
in the table of contents generated from our proposal repository, by
unilaterally rejecting - without any fuhrer comment - technically well
constructed proposals which are guaranteed to be rejected based on
prior discussions in the community, as spam. I think this is already
how it works, but we haven't actually written down this part of the
norms.
Since censorship is always a concern, it would be appropriate to
maintain a moderation log of spam BIPs, so that observers could judge
whether the BIP Editor is misusing the BIP assignment process to
censor proposals with some merit. Since one of the requirements for
submitting a BIP is to notify bitcoin-dev, the log is already
maintained. Since bitcoin-dev is moderated, the moderators take on a
low level of responsibility for gauging spam proposals (and they are
pretty relaxed about it, since it is better to err on the side of
inclusion for new developers, except for obvious patent bombing).
Since the bitcoin-dev moderation log is public and anyone can
subscribe to it, protective transparency is again achieved.
https://lists.ozlabs.org/pipermail/bitcoin-dev-moderation/
|
