From: Ryan Grant <bitcoin-dev@rgrant.org>
To: Keagan McClelland <keagan.mcclelland@gmail.com>,
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 15:27:23 +0000 [thread overview]
Message-ID: <CAMnpzfo+806g+Be=_h31fjZHZZWsv7njT--U3cwgeprhBK7g5Q@mail.gmail.com> (raw)
In-Reply-To: <CALeFGL2Orc6F567Wd9x7o1c5OPyLTV-RTqTmEBrGNbEz+oPaOQ@mail.gmail.com>
We had a UTXO proof-of-stake website at some point during the
blocksize wars. A few people signed with a few thousand bitcoins, but
it was clear that most were not participating. I don't have a link.
Another old discussion link:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2013-June/002731.html
Erik Aronesty listed good issues, a few minutes ago.
Other issues:
- you're feeding the Chainalysis beasts, when hodlers move their UTXOs;
- signalling should be weighted by Bitcoin Days Destroyed [ref_bdd];
- Coinbase.com's interests are not sufficiently aligned to poll them; and
- yuk, it's voting.
Without supporting voting, I wish to note there is also one more way
to de-Sybil, via network analysis, historically labeled the Web of
Trust. It can be algorithmically blinded so as not to fit strongly
into your "KYC" category, despite using assertions about people that
do know each other as a ground truth.
[ref_bdd:]
https://en.bitcoin.it/wiki/Bitcoin_Days_Destroyed
next prev parent reply other threads:[~2022-04-27 15:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 19:37 [bitcoin-dev] Towards a means of measuring user support for Soft Forks 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
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 [this message]
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='CAMnpzfo+806g+Be=_h31fjZHZZWsv7njT--U3cwgeprhBK7g5Q@mail.gmail.com' \
--to=bitcoin-dev@rgrant.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=keagan.mcclelland@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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