From: rob.golding@astutium•com
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Possible Solution To SM Attack
Date: Wed, 06 Nov 2013 00:37:49 +0000 [thread overview]
Message-ID: <d6579e23aae6c3d56d108e24242dad09@astutium.com> (raw)
In-Reply-To: <N1-9eAtMHauq2@Safe-mail.net>
> The Problem:
> Say Alice built a block, A1, from previous block 0. She doesn't let
> other miners know about it. She then works on A2 with previous block
> A1. Bob on the other hand is still working on B1 with previous block
> 0. Bob now finds a block and he broadcasts it. The assumption here is
> Alice will be the first miner to hear of this block and she will send
> her previously mined block, A1, to all other miners. By the time Bobs
> block arrives to other miners majority of them will already have
> received Block A1 and Bobs block will most likely be orphaned. Alice
> revealed her block, A1, only when Bob broadcast his block. This means
> she has been mining on block A2 with previous block A1 for longer than
> any other miner thus gaining an advantage without increasing her hash
> rate.
Unless A1 gets orphaned and B1 gets accepted, in which case all the work
done on A2 is 'wasted'.
The question is whether there is any 'real' advantage over time for A
over B.
> What We Know:
> Alice has gained an advantage with time. She mines longer on the valid
> block.
She mines longer on *a* block which *may* become the valid block, yes.
> In order for this attack to work Alice must reveal her previously
> mined block as late as possible, gaining her the most time spent
> working on the valid block. Since she has such good view of the
> Bitcoin network she can wait until a miner finds a block to release
> her previously mined block.
Then the simple 'fix' would be for the block-acceptance to take into
account either the total transactions or the total fees, and for the the
'accepted' block for mining the next block to be the one with the lowest
hash of one of those values if 2 are released to the network at the same
time
That is of of course assuming there is really a problem to fix,
currently I'm not convinced.
Rob
prev parent reply other threads:[~2013-11-06 1:02 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
2013-11-05 23:44 ` Drak
2013-11-06 0:00 ` Gavin Andresen
2013-11-06 0:37 ` rob.golding [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=d6579e23aae6c3d56d108e24242dad09@astutium.com \
--to=rob.golding@astutium$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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