From: Peter Todd <pete@petertodd•org>
To: Milly Bitcoin <milly@bitcoins•info>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap
Date: Thu, 20 Aug 2015 17:58:20 -0700 [thread overview]
Message-ID: <20150821005820.GA27305@muck> (raw)
In-Reply-To: <55D674C1.6000102@bitcoins.info>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
On Thu, Aug 20, 2015 at 08:45:53PM -0400, Milly Bitcoin via bitcoin-dev wrote:
You know, I've noticed you've spent a tremendous amount of time and
energy on this list promoting these kinds of metrics; obviously you're
somewhat of an expert on this compared to the rest of us.
Why don't you look into spearheading one of these analyses yourself to
show us how it's done?
> The idea is to come up with some sort of standardized metric so as
> the tools and issues come up you are comparing similar things.
>
> The first thing you have to do is link "centralization pressure" and
> (pressure to merge with a big miner) to some sort of overall
> decentralization metric. For instance, how much do big miners
> reduce decentralization to begin with? That is a complicated
> analysis on its own. Then you can measure specif use cases with a
> tool like that.
>
> the idea at least is that the metrics do not "take sides" on any
> issue and just provide a measure of whatever it is you are
> measuring.
>
> most of the references have to do with measuring decentralization in
> political systems so a system would need to be developed to apply to
> software projects like Bitcoin:
>
> http://www.sscnet.ucla.edu/polisci/faculty/treisman/Papers/defin.pdf
>
> http://www.hks.harvard.edu/fs/pnorris/Acrobat/stm103%20articles/Schneider_Decentralization.pdf
--
'peter'[:-1]@petertodd.org
00000000000000000402fe6fb9ad613c93e12bddfc6ec02a2bd92f002050594d
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-08-21 0:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 12:13 Upal Chakraborty
2015-08-18 17:26 ` Chris Wardell
2015-08-20 7:31 ` Jorge Timón
2015-08-20 10:23 ` Milly Bitcoin
2015-08-21 0:25 ` Tom Harding
2015-08-21 0:37 ` Peter Todd
2015-08-21 16:52 ` Tom Harding
2015-08-21 22:21 ` Peter Todd
2015-08-21 23:16 ` Tom Harding
2015-08-22 0:01 ` Peter Todd
2015-08-22 3:21 ` Jorge Timón
2015-08-22 6:26 ` Peter Todd
2015-08-23 23:41 ` Tom Harding
2015-08-24 2:27 ` Jorge Timón
2015-08-21 0:45 ` Milly Bitcoin
2015-08-21 0:58 ` Peter Todd [this message]
2015-08-21 1:30 ` Milly Bitcoin
2015-08-21 20:28 ` Jorge Timón
2015-08-21 12:13 ` Sriram Karra
2015-08-21 20:09 ` Jorge Timón
2015-08-18 19:44 ` cedric perronnet
2015-08-18 20:58 ` Danny Thorpe
2015-08-18 21:17 ` Chris Wardell
2015-08-19 17:21 ` Upal Chakraborty
-- strict thread matches above, loose matches on Subject: below --
2015-08-21 21:45 Upal Chakraborty
2015-08-20 15:02 Upal Chakraborty
2015-08-17 11:57 Rodney Morris
2015-08-17 12:38 ` Angel Leon
2015-08-17 12:43 ` Tier Nolan
2015-08-17 9:44 Upal Chakraborty
2015-08-17 9:54 ` Levin Keller
2015-08-17 9:59 ` Patrick Strateman
2015-08-17 10:51 ` Btc Drak
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=20150821005820.GA27305@muck \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=milly@bitcoins$(echo .)info \
/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