public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Kyle Jerviss <kjj@jerviss.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] we can all relax now
Date: Thu, 7 Nov 2013 08:09:20 -0500	[thread overview]
Message-ID: <20131107130920.GA22476@savin> (raw)
In-Reply-To: <527B1E30.9090800@jerviss.org>

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

On Wed, Nov 06, 2013 at 10:59:28PM -0600, Kyle Jerviss wrote:
> Each block that you solve has a reward.  In practice, some blocks
> will be orphaned, so the expected reward is slightly less than the
> nominal reward.  Each second that you delay publishing a block, the
> expected reward drops somewhat.

You don't understand how to read papers.

A good author will state his assumptions. For instance my third
paragraph read:

    Now in a purely inflation subsidy environment, where I don't care about
    the other miners success, of course I should publish. However, if my
    goals are to find *more* blocks than the other miners for whatever
    reason, maybe because transaction fees matter or I'm trying to get
    nLockTime'd announce/commit fee sacrifices, it gets more complicated.

Now that you understand the assumptions made, you can attack the paper
in one of two ways:

1) Show it's wrong.

2) Show its assumptions make it irrelevant.

You've done neither.

-- 
'peter'[:-1]@petertodd.org
0000000000000006d61eb32f3643aa30c2f9647e4e758af84b03abc43f09959f

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

  reply	other threads:[~2013-11-07 13:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06  5:33 [Bitcoin-development] we can all relax now kjj
2013-11-06  9:26 ` Frank F
2013-11-06 11:35 ` Jeff Garzik
2013-11-06 18:06   ` Christophe Biocca
2013-11-07  3:44     ` Peter Todd
2013-11-07  4:15       ` Kyle Jerviss
2013-11-07  4:33         ` Peter Todd
2013-11-07  4:59           ` Kyle Jerviss
2013-11-07 13:09             ` Peter Todd [this message]
2013-11-07  4:56       ` Gavin Andresen
2013-11-07 13:24         ` Peter Todd
2013-11-07 16:14           ` Mike Hearn
2013-11-07 18:28             ` Daniel Lidstrom
2013-11-08 19:49               ` Andreas M. Antonopoulos
2013-11-08 20:33                 ` Gregory Maxwell
2013-11-15 10:58               ` Peter Todd
2013-11-07  8:07       ` Jannes Faber
2013-11-07  5:24     ` Kyle Jerviss
2013-11-06 18:17 ` Melvin Carvalho
2013-11-06 22:19 ` Jouke Hofman
2014-05-10 11:05 ` E willbefull

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=20131107130920.GA22476@savin \
    --to=pete@petertodd.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=kjj@jerviss.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