From: Anton Ragin <anton@etc-group.com>
To: Karl <gmkarl@gmail.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: Sun, 16 May 2021 21:31:47 +0100 [thread overview]
Message-ID: <CAPyV_jBvbXPPGcCj1TsEf=J9D7ADYWWkTctd9XD5HjJZAQDAfQ@mail.gmail.com> (raw)
In-Reply-To: <CALL-=e45Q_spVnFqVvGAK9c3QzZ=-c_WNwCO-y30q7z-j6orSA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5422 bytes --]
1. Has anyone considered that it might be technically not possible to
completely 'power down' mining rigs during this 'cool-down' period of time?
While modern CPUs have power-saving modes, I am not sure about ASICs used
for mining.
2. I am not a huge data-center specialist, but it was my understanding that
they charge per unit of installed (maximum) electricity consumption. It
would mean that if the miner needs X kilowatts-hour within that 1 minute
when they are allowed to mine, he/she will have to pay for the same X for
the remaining 9 minutes - and as such would have no economic incentive not
to draw that power when idling.
3. Not really a criticism of the idea to reduce Bitcoin energy consumption,
but rather a couple of observations:
(a) Environmental concerns cause Bitcoin to be less popular and thus push
the price lower, which in turn lowers miner's power consumption (lower
Bitcoin price => less they can afford to spend on electricity). So it is a
self-stabilizing system to begin with.
(b) Crazy power consumption may be a temporary problem, after the number of
halving events economic attractiveness of mining will decrease and power
consumption with it.
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:
(a) According to this source (
https://www.blockchain.com/charts/transaction-fees-usd), fees represent
approximately 12.5% of total miner reward. Not a lot, but not insignificant
either.
(b) Based on the method used in this source (
https://digiconomist.net/bitcoin-energy-consumption/) to offset CO2
emissions of bitcoin mining the miner would need to spend approx ~3.6% -
7.2% (depending how 'dirty' is his power source) x 87.5% (mined portion of
its rewards) of its fees (assuming 50k Bitcoin price and 15$ / tonne of CO2
price of carbon offset).
(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*.
Users routing transactions specifically to 'green miners' (and posting
potentially higher fees) would create economic incentives for miners to use
green energy and/or buy CO2 offsets, as described above with ~3.1% - 6.8%
of total revenue cost to offset CO2 vs.12.5% of fees component in mining,
if majority of users would use the routing to green miners method - there
is a chance that Bitcoin network will become significantly greener.
Anton.
On Sun, May 16, 2021 at 8:02 PM Karl via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> [sorry if I haven't replied to the other thread on this, I get swamped
> by email and don't catch them all]
>
> This solution is workable but it seems somewhat difficult to me at this
> time.
>
> The clock might be implementable on a peer network level by requiring
> inclusion of a transaction that was broadcast after a 9 minute delay.
>
> Usually a 50% hashrate attack is needed to reverse a transaction in
> bitcoin. With this change, this naively appears to become a 5%
> hashrate attack, unless a second source of truth around time and order
> is added, to verify proposed histories with.
>
> A 5% hashrate attack is much harder here, because the users of mining
> pools would be mining only 10% of the time, so compromising mining
> pools would not be as useful.
>
> Historically, hashrate has increased exponentially. This means that
> the difficulty of performing an attack, whether it is 5% or 50%, is
> still culturally infeasible because it is a multiplicative, rather
> than an exponential, change.
>
> If this approach were to be implemented, it could be important to
> consider how many block confirmations people wait for to trust their
> transaction is on the chain. A lone powerful miner could
> intentionally fork the chain more easily by a factor of 10. They
> would need to have hashrate that competes with a major pool to do so.
>
> > How would you prevent miners to already compute the simpler difficulty
> problem directly after the block was found and publish their solution
> directly after minute 9? We would always have many people with a finished /
> competing solution.
>
> Such a chain would have to wait a longer time to add further blocks
> and would permanently be shorter.
>
> > Your proposal won’t save any energy because it does nothing to decrease
> the budget available to mine a block (being the block reward).
>
> You are assuming this budget is directly related to energy
> expenditure, but if energy is only expended for 10% of the same
> duration, this money must now be spent on hardware. The supply of
> bitcoin hardware is limited.
>
> In the long term, it won't be, so a 10% decrease is a stop-gap
> measure. Additionally, in the long term, we will have quantum
> computers and AI-designed cryptography algorithms, so things will be
> different in a lot of other ways too.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 6382 bytes --]
next prev parent reply other threads:[~2021-05-16 20:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 21:41 [bitcoin-dev] Proposal: Force to do nothing for first 9 minutes to save 90% of mining energy 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 [this message]
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
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='CAPyV_jBvbXPPGcCj1TsEf=J9D7ADYWWkTctd9XD5HjJZAQDAfQ@mail.gmail.com' \
--to=anton@etc-group.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=gmkarl@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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