public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
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 03:56:57 +0200	[thread overview]
Message-ID: <CAPg+sBjmXyLkgfwzC8h+ZFkmyUf6nzbGo0oAWR9nsJOTOfOXEg@mail.gmail.com> (raw)
In-Reply-To: <CA+i0-i_+Tes+ePRqmDGEXDQ_L=S5y8gHBKk77zaLgTGOS3OMyA@mail.gmail.com>

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



  reply	other threads:[~2013-05-21  1:57 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 [this message]
2013-05-21  3:27     ` Mike Hearn
2013-05-21  3:39       ` Robert Backhaus
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=CAPg+sBjmXyLkgfwzC8h+ZFkmyUf6nzbGo0oAWR9nsJOTOfOXEg@mail.gmail.com \
    --to=pieter.wuille@gmail.com \
    --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