From: Tom Harding <tomh@thinlink•com>
To: Aaron Voisine <voisine@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] SPV clients and relaying double spends
Date: Sat, 27 Sep 2014 19:55:44 -0700 [thread overview]
Message-ID: <542778B0.7090202@thinlink.com> (raw)
In-Reply-To: <CACq0ZD6sMHW6QEHHqDkaZwEwyfuk1CUjb0BRhzt3B+g+8CoP5A@mail.gmail.com>
On 9/25/2014 7:37 PM, Aaron Voisine wrote:
> Of course you wouldn't want nodes to propagate alerts without
> independently verifying them
How would a node independently verify a double-spend alert, other than
by having access to an actual signed double-spend?
#4570 relays the first double-spend AS an alert. Running this branch on
mainnet, I have been keeping a live list of relayed double-spend
transactions at http://respends.thinlink.com
next prev parent reply other threads:[~2014-09-28 3:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 2:02 Aaron Voisine
2014-09-26 2:07 ` Matt Whitlock
2014-09-26 2:12 ` Aaron Voisine
2014-09-26 2:16 ` Matt Whitlock
2014-09-26 2:37 ` Aaron Voisine
2014-09-26 3:34 ` Christophe Biocca
2014-09-28 2:55 ` Tom Harding [this message]
2014-09-28 5:15 ` [Bitcoin-development] replace-by-fee v0.9.3 release Peter Todd
2014-09-28 17:03 ` Luke Dashjr
2014-09-26 16:27 ` [Bitcoin-development] SPV clients and relaying double spends s7r
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=542778B0.7090202@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=voisine@gmail$(echo .)com \
/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