From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <earonesty@gmail.com> Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 1A733C002D for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Apr 2022 20:13:51 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id E712640136 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Apr 2022 20:13:50 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.398 X-Spam-Level: X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=q32-com.20210112.gappssmtp.com 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 iA7jWUM3iRrr for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Apr 2022 20:13:50 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) by smtp2.osuosl.org (Postfix) with ESMTPS id C347A400BA for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Apr 2022 20:13:49 +0000 (UTC) Received: by mail-lf1-x129.google.com with SMTP id x33so5113585lfu.1 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Apr 2022 13:13:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mscHfgsxuqJ02DzBZVK8VL3XzkKdArGapzCf+J9aO5A=; b=slhEe5mRZ/UXE8GtmtiJcvW3Ak4BVQm/1we+qQmYlFcHQ4iqwZR14PE2m/z21zErI6 rf2w8tss8MxG/Up97EPwYfEslGJ4SNglU8rjISebbuarnRcXMzZ4cPkH5iUrD6+ToJ0i O4yEtCIFbboGkEqDNBaoee5htgLlzIAbIIbAq3OXxxwpAzMZVPUCDDxZe2uvl5Tooxmp XyVLQ7O4JRI2sy994p7mAaU9MsKxeMyPTSuKOtGaDK4BeCP1krp8kTMOZSRtZLeRtgDZ r5ZyrncSvjvHLvw5N1YB67FlxtbWL1rGq7EJwNaEExzU9T6aazFAE7sR8YSInVlxYDMz TUdg== 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:cc; bh=mscHfgsxuqJ02DzBZVK8VL3XzkKdArGapzCf+J9aO5A=; b=e1tYycnJPX5kRFIChpltuQnFb//gtWDbvv/fCEP5aaq0M5f1Hw383wZYbDbNEDAmHs MkIdrApkZtPvEMG/VObxTA1rOowjAwJSqxK/oC+yw+QPqrWOMwPt7B1tT5RcYpcN7g1U HHnK6hvwnFkjOpssBW1pRU6lSuq2lbqIjLtXQQ79qNx+hkNAmsomnbUwftImYAJZTTyT /TGeLjFCbKB8djJs6yq7hBU6hvg4gqBI490GjhXsuZx3OeAak4gcM5L3IiU3Na92BcG+ cc1Ry6Kcjvzv9ZTjeV00iDzKnmGPYoWerhGWPtgmhu9lIA9+t2flU+VU7psnLHKF4y0p Ya2Q== X-Gm-Message-State: AOAM532qyFFidEMP3gfOcczhnYg0heQpfDh9nxes6A/kIqo3VsAoMROP 4zMa2gjUK8+YrsTGThi3fmRVg5Whf3AX/98Ez/Nvqik= X-Google-Smtp-Source: ABdhPJz4vcf4VICyzepzVgit5wx6FwFOmFdYCLLazQ2KzT4KdTjlFGT6WNF+VaJKFhe6uCSN+U83omy21KNR8Cgg0yY= X-Received: by 2002:a05:6512:118b:b0:46b:a9ae:3a3b with SMTP id g11-20020a056512118b00b0046ba9ae3a3bmr21892894lfr.188.1651090427338; Wed, 27 Apr 2022 13:13:47 -0700 (PDT) MIME-Version: 1.0 References: <CALeFGL2Orc6F567Wd9x7o1c5OPyLTV-RTqTmEBrGNbEz+oPaOQ@mail.gmail.com> <CABaSBayKH__f_ahUUiDt2SiKik9aNLR1AXtG9RtWrFmTLP5qKw@mail.gmail.com> <CAGpPWDbYj4+g4VPMT9FPqyUZWO+U98YQhgYan5fRqXjpd+dTyw@mail.gmail.com> <CAL5BAw1pKXh4HLrUQByVMwpUtYyWcE5JhjUP-JB_1HKkORB1dA@mail.gmail.com> <CAJowKg+-qy00X_nSvFDz0HtvfjdsaozzGq4Vr8Vbd06GGZ8k_A@mail.gmail.com> <CAGpPWDaDRROKQdQ0WcK-RHo5=dQL6tD=LcQbqfS6p8ZEWkpEmA@mail.gmail.com> In-Reply-To: <CAGpPWDaDRROKQdQ0WcK-RHo5=dQL6tD=LcQbqfS6p8ZEWkpEmA@mail.gmail.com> From: Erik Aronesty <erik@q32.com> Date: Wed, 27 Apr 2022 16:13:35 -0400 Message-ID: <CAJowKgL5kgWkSB=8ioFkfCxmRJLif-P4VSvX04Ubz_h8A3XYtA@mail.gmail.com> To: Billy Tetrud <billy.tetrud@gmail.com> Content-Type: multipart/alternative; boundary="00000000000069e48205dda872ce" X-Mailman-Approved-At: Wed, 27 Apr 2022 20:23:59 +0000 Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> Subject: Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks 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: Wed, 27 Apr 2022 20:13:51 -0000 --00000000000069e48205dda872ce Content-Type: text/plain; charset="UTF-8" > > > > Have you taken a look at my proposal > <https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-March/020146.html>? > The proposal is, to be clear, *not* "voting" but rather polling that isn't > programmatically connected to activation. The intention is for people > (developers) to look at the polling results and make an educated analysis > of it as far as how it should contribute to consensus gathering. > it's cool, and i agree it's somewhat censorship resistant > Let's say everyone who participates in polling broadcasts it along the > bitcoin network (a separate network would probably be better, so as to not > interfere with normal bitcoin, but I digress), > right, anyone can then publish a json file with polling aggregates at a certain block height and anyone can quickly check to see if they are lying or missing data > Similar structures could be added to any script configuration to allow > signing of polls without any significant exposure. > rubin's suggestion around tapscript anon voting could help with anonymity .... all of this is cool ... but it doesn't address the "what about people who don't know there's a vote going on" or other the other social issues with "weighted polling" in general, like how nonexperts can "have a say" when they simply don't understand the relevant issues. i personally feel like i'm "only a very little bit up on the issues" and i have more tech knowledge than most people i know also, it will just be a poll of "people who pay attention to the dev list and maybe some irc rooms" might be worth experimenting with... but unless there's a great ux around the tooling my guess is that it won't garner a lot of meaningful data: open source, simple cli, gitian build, installs easily on all platforms, works well with bitcoind rpc, works with ledger, can import a seed, etc. --00000000000069e48205dda872ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"><div dir=3D"ltr"><div><br><br></div><div>Have you taken = a look at <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-de= v/2022-March/020146.html" target=3D"_blank">my proposal</a>? The proposal i= s, to be clear, *not* "voting" but rather polling that isn't = programmatically connected to activation. The intention is for people (deve= lopers) to look at the polling results and make an educated analysis of it = as far as how it should contribute to consensus gathering.=C2=A0</div></div= ></blockquote><div><br></div><div>it's cool, and i agree it's somew= hat censorship resistant</div><div>=C2=A0</div><blockquote class=3D"gmail_q= uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2= 04);padding-left:1ex"><div dir=3D"ltr"><div>Let's say everyone who part= icipates in polling broadcasts it along the bitcoin network (a separate net= work would probably be better, so as to not interfere with normal bitcoin, = but I digress), </div></div></blockquote><div><br></div><div>right, anyone = can then publish a json file with polling aggregates at a certain block hei= ght and anyone can quickly check to see if they are lying or missing data<b= r>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px= 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D= "ltr"><div>Similar structures could be added to any script configuration to= allow signing of polls without any significant exposure.<br></div></div></= blockquote><div><div><br></div>rubin's suggestion around tapscript=C2= =A0anon voting could help with anonymity<br>=C2=A0<br>.... all of this is c= ool ...</div><div><br></div><div>but it doesn't address the "what = about people who don't know there's a vote going on"=C2=A0 or = other the other social issues with "weighted polling" in general,= like how nonexperts can "have a say" when they simply don't = understand the relevant issues.=C2=A0 i personally feel like i'm "= only a very little bit up on the issues" and i have more tech knowledg= e than most people i know<br><br>also, it will just be a poll of "peop= le who pay attention to the dev list and maybe some irc rooms"<br></di= v></div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><di= v>might be worth experimenting with... but unless there's a great ux ar= ound the tooling my guess is that it won't garner a lot of meaningful d= ata:</div><div><br></div><div>open source, simple cli, gitian build, instal= ls easily on all platforms, works well with bitcoind rpc, works with ledger= , can import a seed, etc.=C2=A0=C2=A0</div><div class=3D"gmail_quote"><br><= /div></div></div> --00000000000069e48205dda872ce--