diff options
| author | Peter Todd <pete@petertodd.org> | 2015-08-20 17:58:20 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2015-08-21 00:58:31 +0000 |
| commit | b90800cf9df04472d52b002c616f3b8176b39683 (patch) | |
| tree | ace7058309fd841b07d08b2f220e65289012da92 | |
| parent | 51a7c61322d006576b43b5475d562015677348a1 (diff) | |
| download | pi-bitcoindev-b90800cf9df04472d52b002c616f3b8176b39683.tar.gz pi-bitcoindev-b90800cf9df04472d52b002c616f3b8176b39683.zip | |
Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap
| -rw-r--r-- | 35/ecabb14f2788cea86e5e4ca004b63a312839b5 | 130 |
1 files changed, 130 insertions, 0 deletions
diff --git a/35/ecabb14f2788cea86e5e4ca004b63a312839b5 b/35/ecabb14f2788cea86e5e4ca004b63a312839b5 new file mode 100644 index 000000000..b9296cd18 --- /dev/null +++ b/35/ecabb14f2788cea86e5e4ca004b63a312839b5 @@ -0,0 +1,130 @@ +Return-Path: <pete@petertodd.org> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 79C0574 + for <bitcoin-dev@lists.linuxfoundation.org>; + Fri, 21 Aug 2015 00:58:31 +0000 (UTC) +X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 +Received: from outmail149080.authsmtp.com (outmail149080.authsmtp.com + [62.13.149.80]) + by smtp1.linuxfoundation.org (Postfix) with ESMTP id 9D86E102 + for <bitcoin-dev@lists.linuxfoundation.org>; + Fri, 21 Aug 2015 00:58:30 +0000 (UTC) +Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) + by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t7L0wSso088858; + Fri, 21 Aug 2015 01:58:28 +0100 (BST) +Received: from muck (s75-157-242-51.bc.hsia.telus.net [75.157.242.51]) + (authenticated bits=128) + by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t7L0wKeA056510 + (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); + Fri, 21 Aug 2015 01:58:26 +0100 (BST) +Date: Thu, 20 Aug 2015 17:58:20 -0700 +From: Peter Todd <pete@petertodd.org> +To: Milly Bitcoin <milly@bitcoins.info> +Message-ID: <20150821005820.GA27305@muck> +References: <CAED3CWgTOMFgaM6bBfU0Dn-R0NrdrhGAQo34wHEneYkTtB4Opg@mail.gmail.com> + <CAEieSeSw04FYCCa-Df+V6BgJo1RHqPvJWt9t=c-JCC=dnhraWA@mail.gmail.com> + <CABm2gDp0o5DBzuoyZ=SFvnBXTwPYFWhdOqUPkP_M_3koNMVP1g@mail.gmail.com> + <55D5AA8E.7070403@bitcoins.info> <55D67017.9000106@thinlink.com> + <55D674C1.6000102@bitcoins.info> +MIME-Version: 1.0 +Content-Type: multipart/signed; micalg=pgp-sha256; + protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" +Content-Disposition: inline +In-Reply-To: <55D674C1.6000102@bitcoins.info> +X-Server-Quench: bbb868a3-479f-11e5-b398-002590a15da7 +X-AuthReport-Spam: If SPAM / abuse - report it at: + http://www.authsmtp.com/abuse +X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR + aAdMdAMUGUATAgsB AmMbW1VeVVV7W2Q7 bA9PbABafEhKXRtv + UVdMSlVNFUssBmAB QWVLIxl3cQBHeDB2 YURiECIJDkx8fRd+ + X0pTHDsbZGY1bX1N U0lQagNUcgZDfk5E bwQuUz1vNG8XDSg5 + AwQ0PjZ0MThBHWx5 UwcEKFMZSEIPD3YX QBYeBzIrGUAJDw8y + MxchK1hUNkIWOUZ6 ClozVBo9Og9aIQRG dwAA +X-Authentic-SMTP: 61633532353630.1023:706 +X-AuthFastPath: 0 (Was 255) +X-AuthSMTP-Origin: 75.157.242.51/587 +X-AuthVirus-Status: No virus detected - but ensure you scan with your own + anti-virus system. +X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW + autolearn=ham version=3.3.1 +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +Cc: bitcoin-dev@lists.linuxfoundation.org +Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Development 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: Fri, 21 Aug 2015 00:58:31 -0000 + + +--n8g4imXOkfNTN/H1 +Content-Type: text/plain; charset=us-ascii +Content-Disposition: inline +Content-Transfer-Encoding: quoted-printable + +On Thu, Aug 20, 2015 at 08:45:53PM -0400, Milly Bitcoin via bitcoin-dev wro= +te: + +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. +>=20 +> 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. +>=20 +> 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. +>=20 +> 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: +>=20 +> http://www.sscnet.ucla.edu/polisci/faculty/treisman/Papers/defin.pdf +>=20 +> http://www.hks.harvard.edu/fs/pnorris/Acrobat/stm103%20articles/Schneider= +_Decentralization.pdf + +--=20 +'peter'[:-1]@petertodd.org +00000000000000000402fe6fb9ad613c93e12bddfc6ec02a2bd92f002050594d + +--n8g4imXOkfNTN/H1 +Content-Type: application/pgp-signature; name="signature.asc" +Content-Description: Digital signature + +-----BEGIN PGP SIGNATURE----- + +iQGrBAEBCACVBQJV1nepXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw +MDAwMDAwMDAwMDAwMDAwNDAyZmU2ZmI5YWQ2MTNjOTNlMTJiZGRmYzZlYzAyYTJi +ZDkyZjAwMjA1MDU5NGQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 +ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udwjhggAgzojukqTiG00pfi60SFiP9JC +73RjErxd7vxCO4YKNuiWNcoeLANpgt1NuCi/MAA1KSt9Ckk7W7YDrZ0oRsGHJCTv +/P7R4AKg/wd0WXWum4ra0Dc9yK/tcf2x876dHlGh2rR7VYGxxXlxKQqdd/bXntQT +Yp7X7m5Eo0ivNzeUjwBbNScucT5hoJzCqbNIEvRJLxuLxPA7kCeFgEW8f3gyL0U4 +YHaEHQKrgW4UW9nUWAhYBAn5Kv2mkcNGSSbXszMFb6PF+K6Ewy6pw2NIaYHJxqNx +n+g/1766Yu0C26CV/WArBrC5G1jIxQIq45stzHkUpaQB4wxYCqZ5iG/RNqKu7g== +=+cuS +-----END PGP SIGNATURE----- + +--n8g4imXOkfNTN/H1-- + |