From: Jeff Garzik <jgarzik@gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] block size - pay with difficulty
Date: Thu, 3 Sep 2015 00:05:11 -0400 [thread overview]
Message-ID: <CADm_Wcb+5Xo3HS-FNUYtCapVpYfVvUS_fxpU0Q=TZHJW1=iAFQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 743 bytes --]
next reply other threads:[~2015-09-03 4:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 4:05 Jeff Garzik [this message]
2015-09-03 4:55 ` [bitcoin-dev] block size - pay with difficulty 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
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='CADm_Wcb+5Xo3HS-FNUYtCapVpYfVvUS_fxpU0Q=TZHJW1=iAFQ@mail.gmail.com' \
--to=jgarzik@gmail.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