public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gavin Andresen <gavinandresen@gmail.com>
To: Drak <drak@zikula.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Possible Solution To SM Attack
Date: Wed, 6 Nov 2013 10:00:04 +1000	[thread overview]
Message-ID: <CABsx9T3LxHy=mqoZQyK+G33ikpbnLyRemBGYn3T22H4dERm4yQ@mail.gmail.com> (raw)
In-Reply-To: <CANAnSg1vrUZPuioZ7LQcSK4MeiWWWQ2nggnDYp5VP4WdhtErhQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

> What do you think?
>

I would like to be convinced that there is, actually, a real-world problem
before thinking about potential solutions.

I'd like to see more analysis of the proposed selfish-mining algorithm at a
particular share-of-network and gamma=0 (assume second-broadcast blocks
always lose, to make the math easier). I can't reproduce the finding in the
paper if I take into account the "opportunity cost" of working on more
blocks in the private chain that might be orphaned instead of always simply
extending the public chain, but it is very possible my little brain is
missing something obvious.

-- 
--
Gavin Andresen

[-- Attachment #2: Type: text/html, Size: 1216 bytes --]

  reply	other threads:[~2013-11-06  0:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 20:51 [Bitcoin-development] Possible Solution To SM Attack 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
2013-11-05 23:44     ` Drak
2013-11-06  0:00       ` Gavin Andresen [this message]
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='CABsx9T3LxHy=mqoZQyK+G33ikpbnLyRemBGYn3T22H4dERm4yQ@mail.gmail.com' \
    --to=gavinandresen@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=drak@zikula.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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