From: Tom Harding <tomh@thinlink•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Superluminal communication and the consensus block size limit
Date: Wed, 5 Aug 2015 20:14:53 -0700 [thread overview]
Message-ID: <55C2D12D.7070302@thinlink.com> (raw)
In-Reply-To: <CABm2gDoF41_1g25F-+ujohGTTFPAZJCX+Xg1QPvt=jYijvb32g@mail.gmail.com>
On 8/5/2015 4:24 PM, Jorge Timón via bitcoin-dev wrote:
> Miner A is able to process 100 M tx/block while miner B is only able
> to process 10 M tx/block.
>
B needs to sell ASICs and buy 90 M tx worth of CPU.
Or, if you cap blocksize at 10 M tx, than A needs to sell the exact same
amount of CPU and buy the exact same amount of ASICs.
Either way, Miner A ends up with the ASIC cost equivalent of 90 M tx
worth of CPU in additional hashing advantage over B. The centralization
has nothing to do with block size. It has to do with Miner A having
more money than Miner B.
Alternatively, you might need to add a few more crazy assumptions.
prev parent reply other threads:[~2015-08-06 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 23:24 Jorge Timón
2015-08-05 23:51 ` Gavin Andresen
2015-08-06 2:33 ` Jorge Timón
2015-08-06 3:14 ` Tom Harding [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=55C2D12D.7070302@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--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