From: Stian Ellingsen <stian@plaimi•net>
To: Btc Ideas <btcideas@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Encouraging good miners
Date: Mon, 27 Mar 2017 19:50:12 +0200 [thread overview]
Message-ID: <c0d518f4-ffb5-704b-02ee-d9587415571c@plaimi.net> (raw)
In-Reply-To: <uQBxE-Qbd-osime4uulMZZHdF_D7usA2EKsPjkTyXCHM0OakN2Wdoeriyrc73yWp5c5ULQNkIsRXAM64cCom7ecPvdwmatOyc9Kh1sTDpl4=@protonmail.com>
On 27/03/17 18:12, Btc Ideas via bitcoin-dev wrote:
> Add a preference for mined blocks to be the one with more
> transactions. This comes into play when 2 blocks of the same height
> are found. The first good block mined would be orphaned if it had
> less transactions than another. Optionally, have this rule apply to
> the current block and the previous one.
This would encourage miners to make their own tiny junk transactions
to fill up their blocks, perhaps leaving larger, more space-efficient
transactions in the mempool.
> This increases incentive for full blocks because a miner thinking
> the faster propagation of a smaller block will win him the reward,
> but that would no longer be a good assumption.
> I read some miners could attack a chain by mining small or empty
> blocks. This makes that a little more difficult, but they can still
> attack the chain many ways.
"Good" miners should probably build upon the block with a set of
transactions more similar to what they themselves would include based
on their mempool at the time. However, miners don't have an incentive
to do so today. Instead, they may be better off building upon the
block that leaves the most valuable transactions in the mempool,
e.g. a small or empty block, and maybe leave some valuable
transactions in the mempool for the next miner.[1] This issue could
possibly be addressed by a soft-fork that requires miners to pay a
portion of their fees to future miners.
[1]
https://freedom-to-tinker.com/2016/10/21/bitcoin-is-unstable-without-the-block-reward/
--
Stian
next prev parent reply other threads:[~2017-03-27 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 16:12 Btc Ideas
2017-03-27 16:29 ` Jameson Lopp
[not found] ` <WM!6b16e14ff3d44b0c6c0030538191fb22c33a979bb09131ef246ffc477e216212e64cfae815c6af871886f74be6b38d7f!@mailhub-mx4.ncl.ac.uk>
[not found] ` <VI1PR0701MB2240F0890E5F19E53CF94B43B5330@VI1PR0701MB2240.eurprd07.prod.outlook.com>
[not found] ` <WM!1f99375705714ae4f8b1288ea47707c53f573e0597317337d41d22e28f801234a0d946b8ef05335cccb825f27bdd72da!@mailhub-mx2.ncl.ac.uk>
2017-03-27 16:29 ` Btc Ideas
2017-03-27 17:29 ` Tom Zander
2017-03-27 20:01 ` Eric Voskuil
2017-03-27 17:50 ` Stian Ellingsen [this message]
2017-03-28 14:38 ` Juan Garavaglia
2017-03-27 20:56 ` Antoine Le Calvez
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=c0d518f4-ffb5-704b-02ee-d9587415571c@plaimi.net \
--to=stian@plaimi$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=btcideas@protonmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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