From: Erik Aronesty <erik@q32•com>
To: Billy Tetrud <billy.tetrud@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
Date: Wed, 27 Apr 2022 16:13:35 -0400 [thread overview]
Message-ID: <CAJowKgL5kgWkSB=8ioFkfCxmRJLif-P4VSvX04Ubz_h8A3XYtA@mail.gmail.com> (raw)
In-Reply-To: <CAGpPWDaDRROKQdQ0WcK-RHo5=dQL6tD=LcQbqfS6p8ZEWkpEmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
>
>
>
> 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.
[-- Attachment #2: Type: text/html, Size: 2799 bytes --]
next prev parent reply other threads:[~2022-04-27 20:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 19:37 Keagan McClelland
2022-04-26 20:39 ` Bryan Bishop
2022-04-27 3:04 ` Billy Tetrud
2022-04-27 14:01 ` Chris Riley
2022-04-27 14:28 ` Erik Aronesty
2022-04-27 16:17 ` Billy Tetrud
2022-04-27 20:13 ` Erik Aronesty [this message]
2022-04-28 5:18 ` Billy Tetrud
2022-04-28 16:09 ` Billy Tetrud
2022-04-28 16:35 ` Billy Tetrud
2022-04-30 6:14 ` ZmnSCPxj
2022-05-01 22:41 ` Billy Tetrud
2022-04-27 15:27 ` Ryan Grant
2022-04-27 17:22 ` micaroni
2022-04-27 18:32 ` Keagan McClelland
2022-04-28 5:26 ` ZmnSCPxj
2022-04-28 8:03 ` micaroni
2022-04-27 17:54 ` Jeremy Rubin
2022-04-28 0:16 ` Nadav Ivgi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJowKgL5kgWkSB=8ioFkfCxmRJLif-P4VSvX04Ubz_h8A3XYtA@mail.gmail.com' \
--to=erik@q32$(echo .)com \
--cc=billy.tetrud@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox