MIME-Version: 1.0
Sender: dscotese@gmail.com
Date: Fri, 11 Sep 2015 09:27:25 -0700
Message-ID: <CAGLBAhd11-_LNJ-ba6NXmWBXz=yb+pFTmf9tHAgFW_m6S5jnfw@mail.gmail.com>
From: Dave Scotese <dscotese@litmocracy.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11c37e46e90773051f7b30ef
Subject: [bitcoin-dev] Bitcoin Days Destroyed as block selection heuristic
Precedence: list

--001a11c37e46e90773051f7b30ef
Content-Type: text/plain; charset=UTF-8

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

--001a11c37e46e90773051f7b30ef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Rather than (promising to, and when they don&#39;t ac=
tually, at least pretending to) use the first-seen block, I propose that a =
more sophisticated method of choosing which of two block solutions to accep=
t.=C2=A0 Essentially, a miner receiving two solutions at the same height wo=
uld compute a weighted sum of bitcoin-days-destroyed (transactions received=
 earlier get higher weights) of whatever transactions are in a block <i>and=
 also</i> were in the miner&#39;s mempool <i>before</i> the first solution =
arrived.=C2=A0 Whichever block has more wins.<br><br></div>This strategy av=
oids allowing miners to use private transactions to mess with the blockchai=
n.=C2=A0 It also makes an empty block far less attractive because it is eas=
ily replaced, all the way until the next block locks it in.=C2=A0 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.<br><div><di=
v><br>I asked<a href=3D"http://bitcoin.stackexchange.com/questions/39226/ca=
n-bitcoin-days-destroyed-be-a-better-resolution-mechanism-for-competing-blo=
cks" class=3D""> Can Bitcoin Days Destroyed be a better resolution mechanis=
m for competing blocks?</a> on the stackexchange bitcoin site in order to c=
ollect objections to and problems with this idea, and have not found any th=
at I haven&#39;t addressed.=C2=A0 The best objection is that <i>maybe</i> e=
mpty blocks and selfish mining are either good for bitcoin, or else they ar=
e so minimally bad that no effort ought to be expended in preventing them.<=
br><br></div><div>If anyone here thinks this is a good idea, and no one can=
 offer reasons it&#39;s a bad idea, I will probably start working on an imp=
lementation.=C2=A0 I&#39;m really slow though, so ping me if it looks like =
fun to you.<br><br></div><div>notplato<br></div></div></div>

--001a11c37e46e90773051f7b30ef--