public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Harding <tomh@thinlink.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] block size - pay with difficulty
Date: Thu, 3 Sep 2015 11:23:11 -0700	[thread overview]
Message-ID: <55E8900F.4050007@thinlink.com> (raw)
In-Reply-To: <CADm_Wcb+5Xo3HS-FNUYtCapVpYfVvUS_fxpU0Q=TZHJW1=iAFQ@mail.gmail.com>

On 9/2/2015 9:05 PM, Jeff Garzik via bitcoin-dev wrote:
> Schemes proposing to pay with difficulty / hashpower to change block 
> size should be avoided.  The miners incentive has always been fairly 
> straightforward - it is rational to deploy new hashpower as soon as 
> you can get it online.  Introducing the concepts of (a) requiring 
> out-of-band collusion to change block size and/or (b) requiring miners 
> to have idle hashpower on hand to change block size are both 
> unrealistic and potentially corrosive.  That potentially makes the 
> block size - and therefore fee market - too close, too sensitive to 
> the wild vagaries of the mining chip market.
>
> Pay-to-future-miner has neutral, forward looking incentives worth 
> researching.
>

Another market dependency is even more direct.

Blocksize that can be bought with either difficulty or bitcoin has 
incentives whose strength (though not direction) is subject to the 
exchange rate.  Hence those incentives are subject to the whims of fiat 
holders, who can push the exchange rate around.



      parent reply	other threads:[~2015-09-03 18:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  4:05 [bitcoin-dev] block size - pay with difficulty Jeff Garzik
2015-09-03  4:55 ` jl2012
2015-09-03 14:18   ` Jeff Garzik
2015-09-03 18:24     ` jl2012
2015-09-03  6:57 ` Gregory Maxwell
2015-09-03 14:31   ` Jeff Garzik
2015-09-03 14:40     ` Jeff Garzik
2015-09-03 17:57       ` Gregory Maxwell
2015-09-03 18:23         ` Jorge Timón
2015-09-03 18:28           ` Btc Drak
2015-09-03 19:17           ` Gregory Maxwell
2015-09-03 18:23 ` 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=55E8900F.4050007@thinlink.com \
    --to=tomh@thinlink.com \
    --cc=bitcoin-dev@lists.linuxfoundation.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