public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mark Friedenbach <mark@monetize.io>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Double-spending unconfirmed transactions is a lot easier than most people realise
Date: Tue, 22 Apr 2014 23:35:06 -0700	[thread overview]
Message-ID: <53575F1A.2000504@monetize.io> (raw)
In-Reply-To: <CABh=4qMk5RbM9pErQd9EsabWo8uP9u82yZOXk87AxdmAPq8H_Q@mail.gmail.com>



On 04/22/2014 09:29 PM, Jan Møller wrote:
>>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?
> 

Because you only want to double-spend if you loss the bet. If you tried
to double-spend every bet, there'd be no point :)



  reply	other threads:[~2014-04-23  6:35 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
2014-04-23  6:35   ` Mark Friedenbach [this message]
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=53575F1A.2000504@monetize.io \
    --to=mark@monetize.io \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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