public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail•com>
To: Drak <drak@zikula•org>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Possible Solution To SM Attack
Date: Tue, 5 Nov 2013 15:06:52 -0800	[thread overview]
Message-ID: <CAAS2fgTofL7ura17KjUR5pL_fOOM=a0gdZTZ7seVMRPOPi66xw@mail.gmail.com> (raw)
In-Reply-To: <CANAnSg2sUfRH0mYEir_XKUz-iOYRpdzNgM-AJ7t-H=SOa4wBig@mail.gmail.com>

On Tue, Nov 5, 2013 at 2:15 PM, Drak <drak@zikula•org> wrote:
> If I understand the issue properly, this seems like a pretty elegant
> solution: if two blocks are broadcast within a certain period of eachother,
> chose the lower target. That's a provable fair way of randomly choosing the
> winning block and would seem like a pretty simply patch.

uh. and so when my solution is, by chance, unusually low... I am
incentivized to hurry up and release my block because?

I've simulated non-first-block-heard strategies in the past (in the
two nearly tied miner with network latency model) and they result in
significant increase in large (e.g. >>6 block) reorgs). It's easy to
make convergence worse or to create additional perverse incentives.



  reply	other threads:[~2013-11-05 23:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 20:51 colj
2013-11-05 22:07 ` Quinn Harris
2013-11-05 23:03   ` Drak
2013-11-06  0:26     ` Quinn Harris
2013-11-05 22:15 ` Drak
2013-11-05 23:06   ` Gregory Maxwell [this message]
2013-11-05 23:44     ` Drak
2013-11-06  0:00       ` Gavin Andresen
2013-11-06  0:37 ` rob.golding

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='CAAS2fgTofL7ura17KjUR5pL_fOOM=a0gdZTZ7seVMRPOPi66xw@mail.gmail.com' \
    --to=gmaxwell@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=drak@zikula$(echo .)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