From: Ryan Grant <bitcoin-dev@rgrant•org>
To: Lonero Foundation <loneroassociation@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST Datastore for Energy Efficient Mining
Date: Fri, 5 Mar 2021 13:42:22 +0000 [thread overview]
Message-ID: <CAMnpzfop8ttqjMAKoS37zpQV6WiZfi1Bn+y_e-HaepTiD4Vm1Q@mail.gmail.com> (raw)
In-Reply-To: <CA+YkXXxUdZFYTa1c-F=-FzoQQVtV3GUmE2Okec-zRAD3xS1qAQ@mail.gmail.com>
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/
next prev parent reply other threads:[~2021-03-05 13:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 23:42 Lonero Foundation
2021-03-05 13:42 ` Ryan Grant [this message]
[not found] ` <CAB0O3SVNyr_t23Y0LyT0mSaf6LONFRLYJ8qzO7rcdJFnrGccFw@mail.gmail.com>
2021-03-05 15:12 ` Lonero Foundation
2021-03-05 16:16 ` Lonero Foundation
2021-03-05 21:11 ` Keagan McClelland
2021-03-05 21:21 ` Lonero Foundation
2021-03-06 0:41 ` Keagan McClelland
2021-03-06 0:57 ` Lonero Foundation
2021-03-06 15:21 ` Ricardo Filipe
[not found] ` <CA+YkXXyP=BQ_a42J=RE7HJFcJ73atyrt4KWKUG8LbsbW=u4b5w@mail.gmail.com>
2021-03-08 23:40 ` Lonero Foundation
2021-03-11 15:29 ` Lonero Foundation
2021-03-12 15:02 ` Erik Aronesty
2021-03-12 16:54 ` Lonero Foundation
2021-03-12 22:37 ` email
2021-03-12 23:21 ` Lonero Foundation
2021-03-12 23:31 ` Lonero Foundation
2021-03-13 8:13 ` email
2021-03-13 15:02 ` Lonero Foundation
2021-03-13 15:45 ` yancy
2021-03-13 17:11 ` Lonero Foundation
2021-03-13 19:44 ` email
2021-03-14 5:45 ` Lonero Foundation
2021-03-17 0:24 ` Erik Aronesty
2021-03-17 5:05 ` ZmnSCPxj
2021-03-17 5:59 ` Lonero Foundation
2021-03-17 6:56 ` ZmnSCPxj
2021-03-17 7:06 ` Lonero Foundation
2021-03-14 12:36 ` LORD HIS EXCELLENCY JAMES HRMH
2021-03-14 14:32 ` Thomas Hartman
2021-03-16 18:22 ` Lonero Foundation
2021-03-15 2:02 ` Eric Martindale
2021-03-15 2:32 ` Lonero Foundation
[not found] ` <CA+YkXXyMUQtdSvjuMPQO71LpPb8qFdy-LTSrA8FEbeWMbPWa4w@mail.gmail.com>
2021-03-15 2:58 ` Lonero Foundation
2021-03-05 20:53 Eric Voskuil
[not found] <CA+YkXXzfEyeXYMyPKL20S+2VVRZVuHRT6eRgX56FBgG_A+uVSw@mail.gmail.com>
[not found] ` <12480994-451A-4256-8EFA-4741B3EC2006@voskuil.org>
2021-03-05 22:03 ` Lonero Foundation
2021-03-05 22:49 ` Eric Voskuil
2021-03-05 23:10 ` Lonero Foundation
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMnpzfop8ttqjMAKoS37zpQV6WiZfi1Bn+y_e-HaepTiD4Vm1Q@mail.gmail.com \
--to=bitcoin-dev@rgrant$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=loneroassociation@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox