public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Robert Backhaus <robbak@robbak.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Double Spend Notification
Date: Tue, 21 May 2013 13:39:30 +1000	[thread overview]
Message-ID: <CA+i0-i-8DFUBLpjtpBGrarH72vqX5FgQGkGUYb-Zz7efHehuwA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP1inofLkfcb3q+_yBd6ZX0OGs-mNbcmu9+ECwn5wVD7jw@mail.gmail.com>

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

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.


On 21 May 2013 13:27, Mike Hearn <mike@plan99.net> wrote:

> Indeed, that has been proposed but it's a dumb idea and I'm very sceptical
> it will go anywhere.  Certainly no decision was made. The arguments for it
> are based on some quite faulty thinking about economics. Double spend
> notifications have been proposed a long time ago, I believe Matt has
> indicated some interest in implementing them and that is the right way to
> go.
> On 20 May 2013 18:57, "Pieter Wuille" <pieter.wuille@gmail.com> wrote:
>
>> On Tue, May 21, 2013 at 3:24 AM, Robert Backhaus <robbak@robbak.com>
>> wrote:
>> > So the decision has been made to make 0-conf double spends trivial, so
>> no
>> > one will ever trust 0-confs. If a later transaction appears with a
>> larger
>> > fee, it will be considered to be the valid one, and the first one
>> dropped,
>> > as long as the first one has not been confirmed. This makes undoing a
>> > mistaken transaction possible.
>>
>> This has been suggested, but I know of no such decision having been made.
>>
>> --
>> Pieter
>>
>>
>> ------------------------------------------------------------------------------
>> Try New Relic Now & We'll Send You this Cool Shirt
>> New Relic is the only SaaS-based application performance monitoring
>> service
>> that delivers powerful full stack analytics. Optimize and monitor your
>> browser, app, & servers with just a few lines of code. Try New Relic
>> and get this awesome Nerd Life shirt!
>> http://p.sf.net/sfu/newrelic_d2d_may
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>

[-- Attachment #2: Type: text/html, Size: 3138 bytes --]

  reply	other threads:[~2013-05-21  3:39 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 [this message]
2013-05-21 13:06         ` Peter Todd
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=CA+i0-i-8DFUBLpjtpBGrarH72vqX5FgQGkGUYb-Zz7efHehuwA@mail.gmail.com \
    --to=robbak@robbak.com \
    --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