From: Gregory Maxwell <gmaxwell@gmail•com>
To: Tom Harding <tomh@thinlink•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] DS Deprecation Window
Date: Tue, 28 Oct 2014 02:36:15 +0000 [thread overview]
Message-ID: <CAAS2fgTW9uWewWbdRj6SCCAKU0D30jFiukDL9YPeG4n8LVwoYg@mail.gmail.com> (raw)
In-Reply-To: <544EFEE8.4000000@thinlink.com>
On Tue, Oct 28, 2014 at 2:26 AM, Tom Harding <tomh@thinlink•com> wrote:
> Matt,
>
> You're right, thanks. Without double-spend relay, miner won't know that
> some txes conflict with anything.
Even with that, the miner cannot tell, his only safe option is to
include no transactions at all.
Consider a malicious miner can concurrently flood all other miners
with orthogonal double spends (which he doesn't mine himself). These
other miners will all be spending some amount of their time mining on
these transactions before realizing others consider them
double-spends.
next prev parent reply other threads:[~2014-10-28 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:58 Tom Harding
2014-10-27 20:17 ` Matt Corallo
2014-10-28 2:26 ` Tom Harding
2014-10-28 2:36 ` Gregory Maxwell [this message]
2014-10-28 17:38 ` Tom Harding
2014-11-06 23:50 ` Tom Harding
2014-10-28 6:24 ` Thomas Zander
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=CAAS2fgTW9uWewWbdRj6SCCAKU0D30jFiukDL9YPeG4n8LVwoYg@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=tomh@thinlink$(echo .)com \
/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