Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id C167EC000D for ; Tue, 5 Oct 2021 12:30:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id AFD8783AF1 for ; Tue, 5 Oct 2021 12:30:59 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.8 X-Spam-Level: X-Spam-Status: No, score=-2.8 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-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=nathanalexander.net header.b="Tk/GM8h4"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="MU364Ml+" 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 qH6vuXk5dYhG for ; Tue, 5 Oct 2021 12:30:59 +0000 (UTC) X-Greylist: delayed 00:07:47 by SQLgrey-1.8.0 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by smtp1.osuosl.org (Postfix) with ESMTPS id 0434183AF0 for ; Tue, 5 Oct 2021 12:30:58 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 766C15C0070 for ; Tue, 5 Oct 2021 08:23:11 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 05 Oct 2021 08:23:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= nathanalexander.net; h=to:from:subject:message-id:date :mime-version:content-type:content-transfer-encoding; s=fm3; bh= 3JB/3Zx17sHH/cnQt5tslQArCLCmt88jMeZN0jNBD5A=; b=Tk/GM8h432tm9gnT c/6N2WDp6qHhozNQn684s9O4K1JDIJJV5KhopdY5tQh6AUbAJ+UzuT817y9fGDau ukTM2P8sGIsVlDK8t0ivv24mZqlXCUlfh3QmDWouLqE3jk29VajjxTb3272EPp3Y c/k9sG5WRua2k+GzkH8JAflmdkLgGIkkgMiaC6CVsCizzPNaaTaCuhowYJhW0FLV NXLNy3h106SEksILSEg8j3zfvsRz3abKfYa+viXAlui01p+S15+dABWwLdvkNB1l XNxiC7yMGuMj3UvtLLQiOOfhjCmgKSicolgRksga6uOR9haU62DOA7CiXUD+28eq S48FDA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=3JB/3Z x17sHH/cnQt5tslQArCLCmt88jMeZN0jNBD5A=; b=MU364Ml+f+8ndypBXBRSq5 AG8my2W657xVrFzCpKUsE826Z44nwKzJvbjv2zfytxjeFLKDNscR3D/JHhfD8iWJ ug/e/ZqFhTXb5K+ePWNhs/90DQxWzTBbzYWiIpz0fccb7C6PCSCXxhwT348growe TQxthaZJtnZ3OtljEj/ipjnhv1oyKF57ZKlSpFIlDQBA5tjQnmd3n3xRhZDyIs0L tiIDzBtKPdQ7JPRLRjmjn8t4ZeuJxFFXo35OtNa312RXlLHOyjN1aw3GrqvTM5Qb Ai0Fxp+y+m+L6sUcjQwDeHgihVyCkgOvAjzQjXs0KxtBWTP6+GBQcv6jToE8LP4Q == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudelgedgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefvhffukffffgggtgfgsehtjeertd dtfeejnecuhfhrohhmpefprghthhgrnhcuvfcutehlvgigrghnuggvrhcuoehnthgrsehn rghthhgrnhgrlhgvgigrnhguvghrrdhnvghtqeenucggtffrrghtthgvrhhnpeehlefhge egudduvddvieduuefgleehhfffudfgffehjeehueehfeegvdefleffgeenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnthgrsehnrghthhgrnh grlhgvgigrnhguvghrrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 5 Oct 2021 08:23:10 -0400 (EDT) To: bitcoin-dev@lists.linuxfoundation.org From: Nathan T Alexander Message-ID: Date: Tue, 5 Oct 2021 07:23:09 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Mailman-Approved-At: Tue, 05 Oct 2021 14:09:36 +0000 Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2021 12:30:59 -0000 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