public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: yanmaani@cock.li
To: Michael Fuhrmann <fuhmic@web.de>,
	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: Mon, 17 May 2021 05:17:54 +0000	[thread overview]
Message-ID: <2b26e45240fad320b3ee584551223455@cock.li> (raw)
In-Reply-To: <d35dee03-2d19-e80a-c577-2151938f9203@web.de>

This is silly, but I'll add my take:

This would create the incentive to have chips that are idle 50% of the 
time and work harder 50% of the time. This means miners would buy twice 
the chips to use the same amount of power, for example.

This in turn means a greater portion of your operational costs are spent 
on chips, and a smaller portion on electricity, reducing the incentive 
to use cheaper power and turn off when it's expensive, because you need 
to recoup your investment. That seems like a bad thing.

Here's my proposal: if you want a PoW algorithm that's better for the 
environment, make one where the chips are easier to manufacture, so 
power costs become a greater portion of miner expenditures. Maybe 
SIMON/SPECK would do it. It could also incentivize someone to find that 
NSA backdoor...

On 2021-05-14 21:41, Michael Fuhrmann via bitcoin-dev wrote:
> Hello,
> 
> Bitcoin should create blocks every 10 minutes in average. So why do
> miners need to mine the 9 minutes after the last block was found? It's
> not necessary.
> 
> Problem: How to prevent "pre-mining" in the 9 minutes time window?
> 
> Possible ideas for discussion:
> 
> - (maybe most difficult) global network timer sending a salted hash 
> time
> code after 9 minutes. this enables validation by nodes.
> 
> - (easy attempt) mining jobs before 9 minutes have a 10 (or 100 or just
> high enough) times higher difficulty. so everyone can mine any time but
> before to 9 minutes are up there will be a too high downside. It is 
> more
> efficient to wait then paying high bills. The bitcoin will get a 
> "puls".
> 
> 
> I dont think I see all problems behind these ideas but if there is a
> working solution to do so then the energy fud will find it's end. 
> Saving
> energy without loosing rosbustness.
> 
> 
> 
> :)
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


  parent reply	other threads:[~2021-05-17  5:18 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
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 [this message]
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=2b26e45240fad320b3ee584551223455@cock.li \
    --to=yanmaani@cock.li \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=fuhmic@web.de \
    /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