From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 83715C0012 for ; Sun, 12 Dec 2021 16:43:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 62DA740227 for ; Sun, 12 Dec 2021 16:43:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFHRGfy_MXGR for ; Sun, 12 Dec 2021 16:43:27 +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 smtp2.osuosl.org (Postfix) with ESMTPS id 2532D400CE for ; Sun, 12 Dec 2021 16:43:26 +0000 (UTC) Received: from mail-lf1-f46.google.com (mail-lf1-f46.google.com [209.85.167.46]) (authenticated bits=0) (User authenticated as jlrubin@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1BCGhOmB007172 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 12 Dec 2021 11:43:25 -0500 Received: by mail-lf1-f46.google.com with SMTP id t26so26812866lfk.9 for ; Sun, 12 Dec 2021 08:43:25 -0800 (PST) X-Gm-Message-State: AOAM533fGsJSVZDqdk3FYWgaLGYWsn+BsJiOzurbKlWYpvLrTU1Mh7Zp TKe4mJWODez4VwFrorAH2CblH3TdJC9jzGZ972g= X-Google-Smtp-Source: ABdhPJxewg7BRnb1w+Iz0083HtM3FMNTwL4oBJyES9TS1Rt68xvvVddWUCER0e9YiUVYeU/s7Ey8oSfLKyUpfXzvm/A= X-Received: by 2002:ac2:5615:: with SMTP id v21mr25617219lfd.112.1639327403734; Sun, 12 Dec 2021 08:43:23 -0800 (PST) MIME-Version: 1.0 From: Jeremy Date: Sun, 12 Dec 2021 08:43:12 -0800 X-Gmail-Original-Message-ID: Message-ID: To: Bitcoin development mailing list Content-Type: multipart/alternative; boundary="00000000000091faa105d2f5a79e" Subject: [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: Sun, 12 Dec 2021 16:43:28 -0000 --00000000000091faa105d2f5a79e Content-Type: text/plain; charset="UTF-8" Howdy, welcome to day 15! Today's post covers a form of a mining pool that can be operated as sort of a map-reduce over blocks without any "infrastructure". https://rubin.io/bitcoin/2021/12/12/advent-15/ There's still some really open-ended questions (perhaps for y'all to consider) around how to select an analyze the choice of window and payout functions, but something like this could alleviate a lot of the centralization pressures typically faced by pools. Notably, compared to previous attempts, combining the payment pool payout with this concept means that there is practically very little on-chain overhead from this approach as the chain-load for including payouts in every block is deferred for future cooperation among miners. Although that can be considered cooperation itself, if you think of it like a pipeline, the cooperation happens out of band from mining and block production so it really is coordination free to mine. Cheers, Jeremy -- @JeremyRubin --00000000000091faa105d2f5a79e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Howdy, welcome to day 15!=

Today's post covers a form of a mining pool that can be operated= as sort of a map-reduce over blocks without any "infrastructure"= .

https://= rubin.io/bitcoin/2021/12/12/advent-15/

There's still some really open-ended q= uestions (perhaps for y'all to consider) around how to select an analyz= e the choice of window and payout functions, but something like this could = alleviate a lot of the centralization pressures typically faced by pools.

Notably, compared to previous attempts, combining the payment po= ol payout with this concept means that there is practically very little on-= chain overhead from this approach as the chain-load
for including payouts in every block is deferred for futu= re cooperation among miners. Although that can be considered cooperation it= self, if you think of it like a pipeline, the cooperation happens out of ba= nd from mining and block production so it really is coordination free to mi= ne.


Cheer= s,

Jeremy

--00000000000091faa105d2f5a79e--