From: Antoine Le Calvez <antoine@alc•io>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Encouraging good miners
Date: Mon, 27 Mar 2017 21:56:49 +0100 [thread overview]
Message-ID: <3cf94d94-f5c9-602e-a8f5-1fe8686468b1@alc.io> (raw)
In-Reply-To: <uQBxE-Qbd-osime4uulMZZHdF_D7usA2EKsPjkTyXCHM0OakN2Wdoeriyrc73yWp5c5ULQNkIsRXAM64cCom7ecPvdwmatOyc9Kh1sTDpl4=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
I don't think encouraging mining more transactions is a good idea since
it would promote inefficient transaction patterns. It's more efficient
to send transactions with a high number of outputs/inputs instead of
creating long transaction chains as some services do.
You might consider incentivizing miners to mine blocks that reduce the
UTXO set size the most, or some other metric that promotes efficient
uses of the blockchain.
On 27/03/17 17: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 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.
>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 2636 bytes --]
prev parent reply other threads:[~2017-03-27 21:24 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
2017-03-28 14:38 ` Juan Garavaglia
2017-03-27 20:56 ` Antoine Le Calvez [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=3cf94d94-f5c9-602e-a8f5-1fe8686468b1@alc.io \
--to=antoine@alc$(echo .)io \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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