Return-Path: <rsomsen@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 56D02C000D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Oct 2021 14:42:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 5100683D8A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Oct 2021 14:42:54 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id nwT7DAoBDz0r
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Oct 2021 14:42:53 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com
 [IPv6:2607:f8b0:4864:20::b33])
 by smtp1.osuosl.org (Postfix) with ESMTPS id 5F89A83D88
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Oct 2021 14:42:53 +0000 (UTC)
Received: by mail-yb1-xb33.google.com with SMTP id u32so46060039ybd.9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 05 Oct 2021 07:42:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=RKbDpC02wHPXwjkOHRhXE777yktov1YH/ZE6hD1Kkio=;
 b=pKE1GldDRI47A4L2U7LPGVVkM76vBQD0O0wydzGAJoGZWIldJB+BKalJ+sXAWSOwrM
 aEcIMvTnbjRnHASB4lwXWjHlsbRkxqJp900xs4RQCXlPtgf48+VSj874gCDbsOWef+7x
 SZmE4lLrscYrBNN0aGBjA90E7jSSQsSgvF8+hPhoM9uxSfTOekQQwM3CrMrmjM7ch+2B
 eOAPKt6z8dStwoE+zE+8OgOGORLRWudua1LFzcHQEA5e+xTU6PlAJktCJs2EnFXUPA8d
 wbL6EQr1tKTVAxMIvLGL9Nwen3K0ZnSFsbiP5hySJbzggI3mk598jKmkkeSRN5nKwwSK
 VBdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=RKbDpC02wHPXwjkOHRhXE777yktov1YH/ZE6hD1Kkio=;
 b=HZscaZSEQYXZl/ZJn2YkWX+2iL9hcAlHlBzMacUFh/QalIPfCM1fYtIkzAIT037ynK
 OacEe6bcRDiSglXTSqMY8bVGmHf0BRPF5Tiw1EZEKV7ceGUsydY2tCyEIvuRbM6HlPuw
 BwHJZDX0CFd2AgadzuYS+Uc4255bY0khbdwvnFtkiVeOBg5gneKNkquf31pcOZeGIFfy
 5zdUMANnpfQ4THknxbD8v0zhQUAxlF315wFfQEi5ARE3MIUYsTeUJmcLEuVDeWt9n/aq
 4kEWK+9eV/EjTRXHk9ankAmBK4nM41SaU7Fb8/dMk17d+Mtldh048I65IHNQiwoRnZYc
 hk4g==
X-Gm-Message-State: AOAM530lWDeFRFhtM+pJgWSYV5Fd0Q1o15C1napA5N66pkvbEuAKXaAp
 YESauG5jLDAbsUJpQiMsIyz69pPQ6uDNoR5hy0rJ9zJiDRg=
X-Google-Smtp-Source: ABdhPJzoiJ5t5TtVE+7HokdLJYEg2/o6GOGHS+p3J0lYI70tNbimMepqvYL/eCk6SkeTujJ/EH3WMedlBR7m7n0ahOM=
X-Received: by 2002:a25:7ec4:: with SMTP id z187mr22599336ybc.35.1633444972093; 
 Tue, 05 Oct 2021 07:42:52 -0700 (PDT)
MIME-Version: 1.0
References: <f867f949-9a04-329b-ea1b-26201f46d2ab@nathanalexander.net>
In-Reply-To: <f867f949-9a04-329b-ea1b-26201f46d2ab@nathanalexander.net>
From: Ruben Somsen <rsomsen@gmail.com>
Date: Tue, 5 Oct 2021 16:42:40 +0200
Message-ID: <CAPv7TjZA2KYeVnT6PE6UHXwPy__E-VOvjmYD1207f1CgBRhLZg@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>, 
 Nathan T Alexander <nta@nathanalexander.net>
Content-Type: multipart/alternative; boundary="0000000000005264d805cd9c0b11"
X-Mailman-Approved-At: Tue, 05 Oct 2021 14:43:32 +0000
Subject: Re: [bitcoin-dev] Question- must every mining rig attempt every
	block?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2021 14:42:54 -0000

--0000000000005264d805cd9c0b11
Content-Type: text/plain; charset="UTF-8"

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
>

--0000000000005264d805cd9c0b11
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Nathan,<div><br></div><div>That&#39;s a fair question, =
but note that we&#39;ve already had a bunch of &quot;green mining&quot; rel=
ated posts a few months ago, so I suspect you&#39;ll be able to find many c=
riticisms to this idea in the following thread:</div><div><br></div><div><a=
 href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/0=
18937.html">https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-Ma=
y/018937.html</a></div><div><br></div><div>It also looks like you&#39;ll be=
 able to find some related answers on Bitcoin Stack Exchange:</div><div><a =
href=3D"https://bitcoin.stackexchange.com/questions/106308/decreasing-energ=
y-consumption-of-bitcoins-pow-with-paired-mining-rounds">https://bitcoin.st=
ackexchange.com/questions/106308/decreasing-energy-consumption-of-bitcoins-=
pow-with-paired-mining-rounds</a><br></div><div><br></div><div>And generall=
y speaking these types of discussions don&#39;t end up being very fruitful =
for bitcoin-dev, because these are the types of changes that are unlikely t=
o ever be seriously considered for Bitcoin.</div><div><br></div><div>Cheers=
,</div><div>Ruben</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
" class=3D"gmail_attr">On Tue, Oct 5, 2021 at 4:09 PM Nathan T Alexander vi=
a bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">=
bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">For purposes of conserving energy, cou=
ldn&#39;t each mining rig have some <br>
non-gameable attribute which would be used to calculate if a block would <b=
r>
be accepted by that rig?<br>
<br>
Don&#39;t the mining rigs have to be able to identify themselves to the <br=
>
network somehow, in order to claim their block reward? Could their <br>
bitcoin network ID be used as a non-gameable attribute?<br>
<br>
Essentially a green light / red light system. In order for a block to be <b=
r>
accepted by the network, it must have all attributes of a successful <br>
block today, and it must also have come from a rig that had a green light.<=
br>
<br>
Perhaps hash some data from the last successful block, along with the <br>
miners non-gameable attribute, and if it&#39;s below a certain number set b=
y <br>
algorithm, the miner gets a green light to race to produce a valid block.<b=
r>
<br>
Nathan Alexander<br>
<br>
Arlington, TX<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--0000000000005264d805cd9c0b11--