From: Ruben Somsen <rsomsen@gmail•com>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Nathan T Alexander <nta@nathanalexander•net>
Subject: Re: [bitcoin-dev] Question- must every mining rig attempt every block?
Date: Tue, 5 Oct 2021 16:42:40 +0200 [thread overview]
Message-ID: <CAPv7TjZA2KYeVnT6PE6UHXwPy__E-VOvjmYD1207f1CgBRhLZg@mail.gmail.com> (raw)
In-Reply-To: <f867f949-9a04-329b-ea1b-26201f46d2ab@nathanalexander.net>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
Hi Nathan,
That's a fair question, but note that we've already had a bunch of "green
mining" related posts a few months ago, so I suspect you'll be able to find
many criticisms to this idea in the following thread:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018937.html
It also looks like you'll be able to find some related answers on Bitcoin
Stack Exchange:
https://bitcoin.stackexchange.com/questions/106308/decreasing-energy-consumption-of-bitcoins-pow-with-paired-mining-rounds
And generally speaking these types of discussions don't end up being very
fruitful for bitcoin-dev, because these are the types of changes that are
unlikely to ever be seriously considered for Bitcoin.
Cheers,
Ruben
On Tue, Oct 5, 2021 at 4:09 PM Nathan T Alexander via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> For purposes of conserving energy, couldn't each mining rig have some
> non-gameable attribute which would be used to calculate if a block would
> be accepted by that rig?
>
> Don't the mining rigs have to be able to identify themselves to the
> network somehow, in order to claim their block reward? Could their
> bitcoin network ID be used as a non-gameable attribute?
>
> Essentially a green light / red light system. In order for a block to be
> accepted by the network, it must have all attributes of a successful
> block today, and it must also have come from a rig that had a green light.
>
> Perhaps hash some data from the last successful block, along with the
> miners non-gameable attribute, and if it's below a certain number set by
> algorithm, the miner gets a green light to race to produce a valid block.
>
> Nathan Alexander
>
> Arlington, TX
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2869 bytes --]
next prev parent reply other threads:[~2021-10-05 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 12:23 Nathan T Alexander
2021-10-05 14:41 ` ZmnSCPxj
2021-10-05 14:42 ` Ruben Somsen [this message]
2021-10-08 15:08 ` Billy Tetrud
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=CAPv7TjZA2KYeVnT6PE6UHXwPy__E-VOvjmYD1207f1CgBRhLZg@mail.gmail.com \
--to=rsomsen@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=nta@nathanalexander$(echo .)net \
/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