public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Anton Ragin <anton@etc-group•com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Force to do nothing for first 9 minutes to save 90% of mining energy
Date: Tue, 18 May 2021 07:46:21 +0000	[thread overview]
Message-ID: <XCHeoYbRg9a2N-IDktDfrJrB-41w3bDRE95UI6MLiRAf48TzRGIN53VEpZqL3atnwGi_g5D3wefYlFH7qrm5ZjPGX3MwvzlaTJKdKN_tCzE=@protonmail.com> (raw)
In-Reply-To: <CAPyV_jDsScGQo4_DB8y7-4ZFGyEqM_Sk3YUUteK6HwPRuxOAvQ@mail.gmail.com>

Good morning Anton,

> >> 4. My counter-proposal to the community to address energy consumption
> >> problems would be *to encourage users to allow only 'green miners' process>> their transaction.* In particular:
> >>...
> >> (b) Should there be some non-profit organization(s) certifying green miners
> >> and giving them cryptographic certificates of conformity (either usage of
> >> green energy or purchase of offsets), users could encrypt their
> >> transactions and submit to mempool in such a format that *only green miners>> would be able to decrypt and process them*.
>
> >Hello centralisation. Might as well just have someone sign miner keys, and get
> >rid of PoW entirely...
> >No, it is not centralization - 
>
> No, it is not centralization, as:
>
> (a) different miners could use different standards / certifications for 'green' status, there are many already;
> (b) it does not affect stability of the network in a material way, rather creates small (12.5% of revenue max) incentive to move to green sources of energy (or buy carbon credits) and get certified - miners who would choose to run dirty energy will still be able to do so.
> and
>
> (c) nothing is being proposed beyond what is already possible - Antpool can go green today, and solicit users to send them signed transactions directly instead of adding them to a public mempool, under the pretext that it would make the transfer 'greener'. What is being proposed is some community effort to standardize & promote this approach, because if we manage to make Bitcoin green(er) - we will remove what many commentators see as the last barrier / biggest risk to even wider Bitcoin adoption.


The point of avoiding centralization is to avoid authorities --- who can end up being bribeable or hackable single points-of-failure, and which would potentially be able to kill Bitcoin as a whole from a single attack point.

Adding an authority which filters miners works directly against this goal, regardless of however you define "centralization" --- centralization is not the root issue here, the authority *is*.

One can observe that "more renewable" energy sources will, economically, be cheaper (in the long run) anyway, and you do not have to add anything to go towards "more green" energy resources.

After all, a "non-renewable" resource is simply a resource that has a lower supply (it cannot be renewed) than a "more renewable" energy source.
There is only so much energy that is stored in coal and oil on Earth, but the sun has a much larger total mass than Earth itself, thus it is a "more renewable" energy resource than coal and oil.
Economically, this implies that "greener" energy resources will be cheaper in the long run, simply by price being a function of supply.

In short: trust the invisible hand.

We already know that lots of miners already operate in places where energy prices have bottomed due to oversupply due to technological improvements in capturing energy that used to be dissipated as waste heat.
What is needed is to spread this knowledge to others, not mess with the design of Bitcoin at a fundamental level and risk introducing unexpected side effects (bugs).


Regards,
ZmnSCPxj


  reply	other threads:[~2021-05-18  7:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 21:41 Michael Fuhrmann
2021-05-15 22:14 ` René Pickhardt
2021-05-15 22:19 ` Pavol Rusnak
2021-05-16 15:30 ` Zac Greenwood
2021-05-16 18:10 ` Karl
2021-05-16 20:31   ` Anton Ragin
2021-05-16 22:06     ` Eric Voskuil
2021-05-16 23:29       ` Karl
2021-05-16 21:15   ` Zac Greenwood
2021-05-16 22:05     ` Karl
2021-05-17  9:34       ` Zac Greenwood
2021-05-17  2:58 ` Luke Dashjr
2021-05-17 12:39   ` Anton Ragin
2021-05-18  7:46     ` ZmnSCPxj [this message]
2021-05-17 19:17   ` Michael Fuhrmann
2021-05-18  8:04     ` ZmnSCPxj
2021-05-17  5:17 ` yanmaani
2021-05-17 13:14 befreeandopen
2021-05-17 13:53 ` Anton Ragin
2021-05-17 17:28   ` Keagan McClelland
2021-05-17 23:02     ` Anton Ragin

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='XCHeoYbRg9a2N-IDktDfrJrB-41w3bDRE95UI6MLiRAf48TzRGIN53VEpZqL3atnwGi_g5D3wefYlFH7qrm5ZjPGX3MwvzlaTJKdKN_tCzE=@protonmail.com' \
    --to=zmnscpxj@protonmail$(echo .)com \
    --cc=anton@etc-group$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /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