From: "Jan Møller" <jan.moller@gmail.com>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Double-spending unconfirmed transactions is a lot easier than most people realise
Date: Wed, 23 Apr 2014 06:29:22 +0200 [thread overview]
Message-ID: <CABh=4qMk5RbM9pErQd9EsabWo8uP9u82yZOXk87AxdmAPq8H_Q@mail.gmail.com> (raw)
In-Reply-To: <20140422213128.GB2578@savin>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
>Of course, this is an especially difficult case, as you must send the
>double-spend after the original transaction - normally just sending a
>non-standard tx to Eligius first would suffice. Note how this defeats
>Andresen's double-spend-relay patch(3) as proposed since the
>double-spend is a non-standard transaction.
Why can't you send a non-standard tx to Eligius first in this scenario?
Is it because LuckyBit is connected directly to Eligius, and does Eligius
relay (not only mine) non-standard transactions?
[-- Attachment #2: Type: text/html, Size: 1317 bytes --]
next prev parent reply other threads:[~2014-04-23 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 21:31 [Bitcoin-development] Double-spending unconfirmed transactions is a lot easier than most people realise Peter Todd
2014-04-23 4:29 ` Jan Møller [this message]
2014-04-23 6:35 ` Mark Friedenbach
2014-04-23 4:45 ` Tom Harding
2014-04-23 4:03 ` Matt Whitlock
2014-04-23 22:29 ` Tom Harding
2014-04-24 0:42 ` Simon Barber
2014-04-23 4:22 ` Jeff Garzik
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='CABh=4qMk5RbM9pErQd9EsabWo8uP9u82yZOXk87AxdmAPq8H_Q@mail.gmail.com' \
--to=jan.moller@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pete@petertodd.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