From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] block-size tradeoffs & hypothetical alternatives (Re: Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it)
Date: Tue, 30 Jun 2015 16:29:36 -0400 [thread overview]
Message-ID: <5592FC30.9090109@bitcoins.info> (raw)
In-Reply-To: <5592F74E.80200@openbitcoinprivacyproject.org>
>"Decentralization" is a popular buzzword these days, but how about
stating the problem description in a way that is more precise and
accurate? One of Bitcoin's differentiating properties is that it
prevents double spending without using a trusted third party.
I have been researching how it can be defined and measured (at least up
to a certain point). Here is a paper on measuring decentralization of
government functions:
http://www.sscnet.ucla.edu/polisci/faculty/treisman/Papers/defin.pdf.
Not exactly the same thing as being discussed here but the paper gives a
framework of how decentralization metrics could be defined in a somewhat
standard way.
Russ
next prev parent reply other threads:[~2015-06-30 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 19:54 Adam Back
2015-06-30 20:08 ` Justus Ranvier
2015-06-30 20:29 ` Milly Bitcoin [this message]
2015-06-30 22:55 ` Simon Liu
2015-06-30 22:56 ` Tom Harding
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=5592FC30.9090109@bitcoins.info \
--to=milly@bitcoins$(echo .)info \
--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