public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Yifu Guo <yifu@coinapex.com>
To: Tom Harding <tomh@thinlink.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Mining centralization pressure from non-uniform propagation speed
Date: Thu, 18 Jun 2015 21:31:00 -0400	[thread overview]
Message-ID: <CAHcfU-WQAqz_tEUSho3TVBdaF8qW=uLZ+eVXb4eiGDDZy9w9ZA@mail.gmail.com> (raw)
In-Reply-To: <55833F87.3090408@thinlink.com>

[-- Attachment #1: Type: text/plain, Size: 3572 bytes --]

Nice insight Peter,

This further confirms the real problem, which doesn't have much to do with
blocksize but rather the connectivity of nodes in countries with
not-so-friendly internet policies and deceptive connectivity.


On Thu, Jun 18, 2015 at 6:00 PM, Tom Harding <tomh@thinlink.com> wrote:

> On 06/12/2015 06:51 PM, Pieter Wuille wrote:
> >> However, it does very clearly show the effects of
> >> larger blocks on centralization pressure of the system.
>
> On 6/14/2015 10:45 AM, Jonas Nick wrote:
> > This means that your scenario is not the result of a cartel but the
> result of a long-term network partition.
> >
>
> Pieter, to Jonas' point, in your scenario the big miners are all part of
> the majority partition, so "centralization pressure" (pressure to merge
> with a big miner) cannot be separated from "pressure to be connected to
> the majority partition".
>
> I ran your simulation with a large (20%) miner in a 20% minority
> partition, and 16 small (5%) miners in a majority 80% partition, well
> connected.  The starting point was your recent update, which had a more
> realistic "slow link" speed of 100 Mbit/s (making all of the effects
> smaller).
>
> To summarize the results across both your run and mine:
>
> ** Making small blocks when others are making big ones -> BAD
> ** As above, and fees are enormous -> VERY BAD
>
> ** Being separated by a slow link from majority hash power -> BAD
>
> ** Being a small miner with blocksize=20MB -> *NOT BAD*
>
>
> Configuration:
>    * Miner group 0: 20.000000% hashrate, blocksize 20000000.000000
>    * Miner group 1: 80.000000% hashrate, blocksize 1000000.000000
>    * Expected average block size: 4800000.000000
>    * Average fee per block: 0.250000
>    * Fee per byte: 0.0000000521
> Result:
>    * Miner group 0: 20.404704% income (factor 1.020235 with hashrate)
>    * Miner group 1: 79.595296% income (factor 0.994941 with hashrate)
>
> Configuration:
>    * Miner group 0: 20.000000% hashrate, blocksize 20000000.000000
>    * Miner group 1: 80.000000% hashrate, blocksize 20000000.000000
>    * Expected average block size: 20000000.000000
>    * Average fee per block: 0.250000
>    * Fee per byte: 0.0000000125
> Result:
>    * Miner group 0: 19.864232% income (factor 0.993212 with hashrate)
>    * Miner group 1: 80.135768% income (factor 1.001697 with hashrate)
>
> Configuration:
>    * Miner group 0: 20.000000% hashrate, blocksize 20000000.000000
>    * Miner group 1: 80.000000% hashrate, blocksize 1000000.000000
>    * Expected average block size: 4800000.000000
>    * Average fee per block: 25.000000
>    * Fee per byte: 0.0000052083
> Result:
>    * Miner group 0: 51.316895% income (factor 2.565845 with hashrate)
>    * Miner group 1: 48.683105% income (factor 0.608539 with hashrate)
>
> Configuration:
>    * Miner group 0: 20.000000% hashrate, blocksize 20000000.000000
>    * Miner group 1: 80.000000% hashrate, blocksize 20000000.000000
>    * Expected average block size: 20000000.000000
>    * Average fee per block: 25.000000
>    * Fee per byte: 0.0000012500
> Result:
>    * Miner group 0: 19.865943% income (factor 0.993297 with hashrate)
>    * Miner group 1: 80.134057% income (factor 1.001676 with hashrate)
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>



-- 
*Yifu Guo*
*"Life is an everlasting self-improvement."*

[-- Attachment #2: Type: text/html, Size: 5194 bytes --]

      reply	other threads:[~2015-06-19  1:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 16:51 [Bitcoin-development] Mining centralization pressure from non-uniform propagation speed Pieter Wuille
2015-06-12 17:21 ` Gavin Andresen
2015-06-12 18:30   ` Peter Todd
2015-06-12 18:39     ` Pieter Wuille
2015-06-12 18:01 ` Peter Todd
2015-06-12 18:24 ` Mike Hearn
2015-06-12 18:26   ` Pieter Wuille
2015-06-12 18:27     ` Mike Hearn
2015-06-14 17:45 ` Jonas Nick
2015-06-18 22:00   ` Tom Harding
2015-06-19  1:31     ` Yifu Guo [this message]

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='CAHcfU-WQAqz_tEUSho3TVBdaF8qW=uLZ+eVXb4eiGDDZy9w9ZA@mail.gmail.com' \
    --to=yifu@coinapex.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=tomh@thinlink.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