From: Robert McKay <robert@mckay•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] A mining pool at 46%
Date: Fri, 05 Apr 2013 11:50:06 +0100 [thread overview]
Message-ID: <bd376018d72b65a64a5124ebc2770d1a@webmail.mckay.com> (raw)
In-Reply-To: <CANEZrP3S7b+uh2LW4vH=53opopLJRmmJ-_Uad6yEQxZ3kHW47A@mail.gmail.com>
On Fri, 5 Apr 2013 11:48:51 +0200, Mike Hearn wrote:
> However, youre somewhat right in the sense that its a self-defeating
> attack. If the pool owner went bad, he could pull it off once, but
> the
> act of doing so would leave a permanent record and many of the people
> mining on his pool would leave. As he doesnt own the actual mining
> hardware, he then wouldnt be able to do it again.
Unless all the miners are monitoring the work they do for their pools
and the actual miners that found the blocks noticed (unlikely) - the
only way anyone knows which pool did anything is the source IP that
first disseminates the new block. Also since it's unlikely that both of
the doublespend blocks would be found by the same end miner, neither of
them would know that the pool operator was responsible even if they were
monitoring their work.
There's nothing stopping the pool owner from channeling the doublespend
blocks through some other previously unknown IP, so I don't think they
would suffer any reputational damage from doing this repeatidly.
Robert
next prev parent reply other threads:[~2013-04-05 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 9:30 Melvin Carvalho
2013-04-05 9:48 ` Mike Hearn
2013-04-05 10:02 ` Gregory Maxwell
2013-04-05 10:13 ` Melvin Carvalho
2013-04-05 12:12 ` Peter Todd
2013-04-08 12:32 ` Daryl Tucker
2013-04-05 10:50 ` Robert McKay [this message]
2013-04-05 9:52 ` Gregory Maxwell
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=bd376018d72b65a64a5124ebc2770d1a@webmail.mckay.com \
--to=robert@mckay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)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