public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Daniele Pinna <daniele.pinna@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] ERRATA CORRIGE + Short Theorem
Date: Tue, 1 Sep 2015 03:56:14 -0400	[thread overview]
Message-ID: <20150901075613.GD17380@muck> (raw)
In-Reply-To: <CAEgR2PE35K6kt1sZ0iDu2Y9vv+6+Omgg_n4n3gtMggYuE3YD-g@mail.gmail.com>

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

On Sun, Aug 30, 2015 at 10:01:00PM +0200, Daniele Pinna via bitcoin-dev wrote:
> Since my longer post seems to be caught in moderator purgatory I will
> rehash its results into this much smaller message. I apologize for the
> spamming.
> 
> I present a theorem whose thesis is obvious to many.
> 
> *THESIS: All hashrates* *h' > h generate a revenue per unit of hash v' >
> v. *
> 
> Let us absurdly[1] assume that an optimal hashrate *h* exists where the
> average revenue for each hash in service is maximized. This will result
> from perpetually mining blocks of size *q,* is *v. *All larger hashrates *h'
> > h* will generate an average revenue per hash *v' < v*(effectively the
> conclusion of my paper) due to the higher orphan risk carried from having
> to mine blocks of size *q' > q*. Leading from Peter's model and my
> analysis, the origin of this balance lies in the fact that larger miners
> must somehow be forced to mine larger blocks which in turn carry a larger
> orphan risk.
> 
> What happens if a large miner *h'* chooses not to mine his optimal block
> size *q' *in favor of a seemingly "sub-optimal" block size* q*?
> Since he mines a block of identical size as the smaller miner, they will
> both carry identical orphan risks[2], and win identical
> amounts*R+M(q)* whenever
> they successfully mine a block. Since the larger miner can statistically
> expect to win *h'/h* more blocks than the smaller miner, they will each
> earn an identical revenue per unit of hash *R+M(q)/h*.
> 
> This however directly contradicts the assumption that an optimal hashrate
> exists beyond which the revenue per unit of hash *v' < v*if  *h' > h. *
> *Q.E.D *
> 
> This theorem in turn implies the following corollary:
> 
> *COROLLARY: **The marginal profit curve is a monotonically increasing of
> miner hashrate.*
> 
> This simple theorem, suggested implicitly by Gmaxwell disproves any and all
> conclusions of my work. Most importantly, centralization pressures will
> always be present.

FWIW I did a quick math proof along those lines awhile back too using
some basic first-year math, again proving that larger miners earn more
money per unit hashing power:

http://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg03272.html

-- 
'peter'[:-1]@petertodd.org
000000000000000010b552c5f5c18705ccb1b21c550c08872089f89076840d6d

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]

  reply	other threads:[~2015-09-01  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30 20:01 [bitcoin-dev] ERRATA CORRIGE + Short Theorem Daniele Pinna
2015-09-01  7:56 ` Peter Todd [this message]
2015-09-01  8:06   ` Peter R
2015-09-01  8:52     ` Daniele Pinna

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=20150901075613.GD17380@muck \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=daniele.pinna@gmail.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