From: Dave Scotese <dscotese@litmocracy•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin Days Destroyed as block selection heuristic
Date: Fri, 11 Sep 2015 09:27:25 -0700 [thread overview]
Message-ID: <CAGLBAhd11-_LNJ-ba6NXmWBXz=yb+pFTmf9tHAgFW_m6S5jnfw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
Rather than (promising to, and when they don't actually, at least
pretending to) use the first-seen block, I propose that a more
sophisticated method of choosing which of two block solutions to accept.
Essentially, a miner receiving two solutions at the same height would
compute a weighted sum of bitcoin-days-destroyed (transactions received
earlier get higher weights) of whatever transactions are in a block *and
also* were in the miner's mempool *before* the first solution arrived.
Whichever block has more wins.
This strategy avoids allowing miners to use private transactions to mess
with the blockchain. It also makes an empty block far less attractive
because it is easily replaced, all the way until the next block locks it
in. Any block-selection heuristic can be gamed, but I believe that using a
weighted sum of BTCDD is harder to game than using block propagation timing.
I asked Can Bitcoin Days Destroyed be a better resolution mechanism for
competing blocks?
<http://bitcoin.stackexchange.com/questions/39226/can-bitcoin-days-destroyed-be-a-better-resolution-mechanism-for-competing-blocks>
on the stackexchange bitcoin site in order to collect objections to and
problems with this idea, and have not found any that I haven't addressed.
The best objection is that *maybe* empty blocks and selfish mining are
either good for bitcoin, or else they are so minimally bad that no effort
ought to be expended in preventing them.
If anyone here thinks this is a good idea, and no one can offer reasons
it's a bad idea, I will probably start working on an implementation. I'm
really slow though, so ping me if it looks like fun to you.
notplato
[-- Attachment #2: Type: text/html, Size: 1832 bytes --]
next reply other threads:[~2015-09-11 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 16:27 Dave Scotese [this message]
2015-09-11 16:32 ` Jorge Timón
2015-09-11 17:18 ` Christophe Biocca
2015-09-11 18:37 ` Jorge Timón
2015-09-11 19:06 ` Christophe Biocca
2015-09-11 19:26 ` Dave Scotese
2015-09-11 22:21 ` Vincent Truong
2015-09-12 18:55 ` Dave Scotese
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='CAGLBAhd11-_LNJ-ba6NXmWBXz=yb+pFTmf9tHAgFW_m6S5jnfw@mail.gmail.com' \
--to=dscotese@litmocracy$(echo .)com \
--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