public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Robert Backhaus <robbak@robbak.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Double Spend Notification
Date: Tue, 21 May 2013 06:06:13 -0700	[thread overview]
Message-ID: <20130521130613.GB27580@tilt> (raw)
In-Reply-To: <CA+i0-i-8DFUBLpjtpBGrarH72vqX5FgQGkGUYb-Zz7efHehuwA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

On Tue, May 21, 2013 at 01:39:30PM +1000, Robert Backhaus wrote:
> That's good - what I had taken away from the replace-by-fee discussions was
> that it was finally decided.
> 
> My opinion is that we should be doing what we can to make 0-confs as
> reliable as possible - which will always be 'not very', but a solid system
> to notify on attempted double-spends is a good start.
> 
> I'd like to know how Peter Todd's experiment with the 2BTC reward has gone.

piuk wrote a double-spender that I think meets the criteria for the
reward: https://blockchain.info/create-double-spend

I'll get a chance to test it properly when I'm back from vacation, but
looks like he's getting the 2BTC. If it does work as intended I'm also
planning on doing a demo/video at the next Toronto Bitcoin Meetup to
demonstrate the attack in a real-life exchange.

-- 
'peter'[:-1]@petertodd.org
00000000000000f31f5cd20f915e3edb8e3fceea49580235b984fea63f1f882c

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-05-21 13:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  0:45 [Bitcoin-development] Double Spend Notification Quinn Harris
2013-05-21  1:24 ` Robert Backhaus
2013-05-21  1:56   ` Pieter Wuille
2013-05-21  3:27     ` Mike Hearn
2013-05-21  3:39       ` Robert Backhaus
2013-05-21 13:06         ` Peter Todd [this message]
2013-05-21  3:54     ` Gregory Maxwell
2013-05-21  4:39       ` Gavin Andresen
2013-05-21  7:04         ` Gregory Maxwell
2013-05-21  8:08           ` Robert Backhaus
2013-05-21 13:05       ` Peter Todd
2013-05-21 14:26         ` David Vorick
2013-05-21 16:47         ` Quinn Harris
2013-05-21  3:46   ` Quinn Harris

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=20130521130613.GB27580@tilt \
    --to=pete@petertodd.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=robbak@robbak.com \
    /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