public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Michael Fuhrmann <fuhmic@web.de>
To: 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 21:17:32 +0200	[thread overview]
Message-ID: <1e048030-36c6-0ae8-7209-516bd797d29c@web.de> (raw)
In-Reply-To: <202105170258.13233.luke@dashjr.org>



Am 17.05.2021 um 04:58 schrieb Luke Dashjr:

> It increases security, and is unavoidable anyway.
>
> You can't.

There must be a way. dRNG + universal clock + cryptographical magic?!
I'll think about more. Because if there is a safe way of knowing when a
block was mined then this can work and no security is lost. The run für
the next coinbase starts now at 0 seconds and should end after 600
seconds. There is no real change if you start (proofable) 540 seconds
later und must finish in 60 seconds. I see this 10 times harder than 10
times softer.

It is just a blocktime of 60 seconds with 9 minutes of idle time.

But for this time thank you for all your great answers :D


:)

ps: it wasnt a pointing fingers musk move. it was the opposite. more
like "we try hard to be more efficient than everything else before even
if we still are".


  parent reply	other threads:[~2021-05-17 19:17 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 [this message]
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=1e048030-36c6-0ae8-7209-516bd797d29c@web.de \
    --to=fuhmic@web.de \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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