public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter R <peter_r@gmx.com>
To: Peter Todd <pete@petertodd.org>
Cc: bitcoin-dev@lists.linuxfoundation.org,
	Daniele Pinna <daniele.pinna@gmail.com>
Subject: Re: [bitcoin-dev] ERRATA CORRIGE + Short Theorem
Date: Tue, 1 Sep 2015 01:06:30 -0700	[thread overview]
Message-ID: <7E54183F-DDBD-4EFB-828B-841350A80E33@gmx.com> (raw)
In-Reply-To: <20150901075613.GD17380@muck>


[-- Attachment #1.1: Type: text/plain, Size: 866 bytes --]

On 2015-09-01, at 12:56 AM, Peter Todd via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote
> 
> 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

I don't believe anyone is arguing otherwise.  Miners with a larger fraction of the network hash rate, h/H, have a theoretical advantage, all other variables in the miner's profitability equation held constant.  

Dpinna originally claimed (unless I'm mistaken) that his paper showed that this advantage decreased as the block reward diminished or as the total fees increased.  This didn't seem unreasonable to me, although I never checked the math.  

Best regards,
Peter


 


[-- Attachment #1.2: Type: text/html, Size: 1438 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

  reply	other threads:[~2015-09-01  8:06 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
2015-09-01  8:06   ` Peter R [this message]
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=7E54183F-DDBD-4EFB-828B-841350A80E33@gmx.com \
    --to=peter_r@gmx.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=daniele.pinna@gmail.com \
    --cc=pete@petertodd.org \
    /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