From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id E4031C0012 for ; Thu, 23 Dec 2021 19:05:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id C4C6483268 for ; Thu, 23 Dec 2021 19:05:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -4.197 X-Spam-Level: X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 XDQZO3t40SOD for ; Thu, 23 Dec 2021 19:05:37 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by smtp1.osuosl.org (Postfix) with ESMTPS id 0CE94831A7 for ; Thu, 23 Dec 2021 19:05:36 +0000 (UTC) Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com [209.85.167.44]) (authenticated bits=0) (User authenticated as jlrubin@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1BNJ5YSu012935 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 23 Dec 2021 14:05:35 -0500 Received: by mail-lf1-f44.google.com with SMTP id u13so14245673lff.12 for ; Thu, 23 Dec 2021 11:05:35 -0800 (PST) X-Gm-Message-State: AOAM531BOnhqM8Qd1Vkef45HnbGJxBhCbHVIPs5L5JRdg9TXQlhvAB+Q JU2dqAENiK24aIHXueEr8VBxyzO/JaynFVFUGpI= X-Google-Smtp-Source: ABdhPJwo4FDrrkk1yey2v6jgIa0G9piqGmVmP39V59oip/AX7Lo6/djHjK20i7oCAGYNmKQkg+469Qx1bZoBc+xN/uk= X-Received: by 2002:a05:6512:210f:: with SMTP id q15mr2902216lfr.112.1640286333727; Thu, 23 Dec 2021 11:05:33 -0800 (PST) MIME-Version: 1.0 References: <151161119-8858833d76ec6beed19cf87cc542dc62@pmq3v.m5r2.onet> In-Reply-To: <151161119-8858833d76ec6beed19cf87cc542dc62@pmq3v.m5r2.onet> From: Jeremy Date: Thu, 23 Dec 2021 11:05:22 -0800 X-Gmail-Original-Message-ID: Message-ID: To: vjudeu@gazeta.pl, Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000004078d105d3d4ec62" Cc: Billy Tetrud Subject: Re: [bitcoin-dev] [Bitcoin Advent Calendar] Decentralized Coordination Free Mining Pools 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: Thu, 23 Dec 2021 19:05:38 -0000 --0000000000004078d105d3d4ec62 Content-Type: text/plain; charset="UTF-8" > If you introduce signing into mining, then you will have cases, where > someone is powerful enough to produce blocks, but cannot, because signing > is needed. Then, your consensus is no longer "the heaviest chain", but "the > heaviest signed chain". That means, your computing power is no longer > enough by itself (as today), because to make a block, you also need some > kind of "permission to mine", because first you sign things (like in > signet) and then you mine them. That kind of being "reliably unreliable" > may be ok for testing, but not for the main network. this is a really great point worth underscoring. this is the 'key ingredient' for DCFMP, which is that there is no signing or other network system that is 'in the way' of normal bitcoin mining, just an opt-in set of rules for sharing the bounties of your block in exchange for future shares. --0000000000004078d105d3d4ec62 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If you introduce signing in= to mining, then you will have cases, where someone is powerful enough to pr= oduce blocks, but cannot, because signing is needed. Then, your consensus i= s no longer "the heaviest chain", but "the heaviest signed c= hain". That means, your computing power is no longer enough by itself = (as today), because to make a block, you also need some kind of "permi= ssion to mine", because first you sign things (like in signet) and the= n you mine them. That kind of being "reliably unreliable" may be = ok for testing, but not for the main network.

this is a really great point worth unders= coring. this is the 'key ingredient' for DCFMP, which is that there= is no signing or other network system that is 'in the way' of norm= al bitcoin mining, just an opt-in set of rules for sharing the bounties of = your block in exchange for future shares.
--0000000000004078d105d3d4ec62--