public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <hearn@vinumeris•com>
To: Arne Brutschy <abrutschy@xylon•de>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
Date: Sat, 18 Jul 2015 13:43:14 +0200	[thread overview]
Message-ID: <CA+w+GKTmBpLYDx+yfW=D4pa40n7qKC8knHMS413MoSfq3Wrafg@mail.gmail.com> (raw)
In-Reply-To: <55A7BFF7.2050608@xylon.de>

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

>
> What are these pre- and post-Hearn-relay drop rules you are speaking
> about?


He's talking about patches I didn't even write (Gavin and Tom did), but
have included in Bitcoin XT:

   https://github.com/bitcoinxt/bitcoinxt

See the README section starting with "Relaying of double spends"

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

  parent reply	other threads:[~2015-07-18 11:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  3:29 simongreen
2015-07-15 14:35 ` Tom Harding
2015-07-15 15:18   ` Peter Todd
2015-07-15 15:49     ` Me
2015-07-15 15:53       ` Bastiaan van den Berg
2015-07-15 15:59       ` Peter Todd
2015-07-15 16:06         ` Me
2015-07-15 16:11           ` Pieter Wuille
2015-07-15 16:41             ` Me
2015-07-15 16:12         ` Milly Bitcoin
2015-07-15 18:25           ` Matthieu Riou
2015-07-15 19:32             ` Peter Todd
2015-07-15 19:57               ` Milly Bitcoin
2015-07-16  0:08               ` Matthieu Riou
2015-07-16  5:18                 ` odinn
2015-07-17 11:59                 ` Peter Todd
2015-07-17 12:56                   ` Milly Bitcoin
2015-07-15 17:01 ` Adrian Macneil
2015-07-16 14:30 ` Arne Brutschy
2015-07-16 14:50   ` Me
2015-07-16 15:33     ` Greg Schvey
2015-07-18 11:43   ` Mike Hearn [this message]
2015-07-18 15:09     ` Peter Todd

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+w+GKTmBpLYDx+yfW=D4pa40n7qKC8knHMS413MoSfq3Wrafg@mail.gmail.com' \
    --to=hearn@vinumeris$(echo .)com \
    --cc=abrutschy@xylon$(echo .)de \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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