From: Gavin Andresen <gavinandresen@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Superluminal communication and the consensus block size limit
Date: Wed, 5 Aug 2015 19:51:03 -0400 [thread overview]
Message-ID: <CABsx9T0Wt7pSx2Qgcu8tSeyQuhBkH=fpLXhj-=UsXHJzqkVKnA@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDoF41_1g25F-+ujohGTTFPAZJCX+Xg1QPvt=jYijvb32g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Wed, Aug 5, 2015 at 7:24 PM, Jorge Timón <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Miner A is able to process 100 M tx/block while miner B is only able
> to process 10 M tx/block.
>
> Will miner B be able to maintain itself competitive against miner B?
>
> The answer is: it depends on the consensus maximum block size.
>
No, it depends on all of the variables that go into the mining
profitability equation.
Does miner B have access to cheaper electricity than miner A?
Access to more advanced mining hardware, sooner?
Ability to use excess heat generated from mining productively?
Access to inexpensive labor to oversee their operations?
Access to inexpensive capital to finance investment in hardware?
The number of fee-paying transactions a miner can profitably include in
their blocks will certainly eventually be part of that equation (it is
insignificant today), and that's fantastic-- we WANT miners to include lots
of transactions in their blocks.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 1695 bytes --]
next prev parent reply other threads:[~2015-08-05 23:51 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 [this message]
2015-08-06 2:33 ` Jorge Timón
2015-08-06 3:14 ` 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='CABsx9T0Wt7pSx2Qgcu8tSeyQuhBkH=fpLXhj-=UsXHJzqkVKnA@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/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