From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] replace-by-fee v0.9.3 release
Date: Sun, 28 Sep 2014 17:03:50 +0000 [thread overview]
Message-ID: <201409281703.51377.luke@dashjr.org> (raw)
In-Reply-To: <20140928051553.GB11287@savin.petertodd.org>
On Sunday, September 28, 2014 5:15:53 AM Peter Todd wrote:
> On Sat, Sep 27, 2014 at 07:55:44PM -0700, Tom Harding wrote:
> > 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
>
> Speaking of, I ported my replace-by-fee branch the recent v0.9.3
> release: https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.9.3
>
> I actually ported it a few days ago; that release has been running on a
> half-dozen or so nodes right now for a few days with no issues.
>
> The v0.9.3 release's scriptSig size limit increase adds a new category
> of double-spending exploit. I'm not going to get time to add that
> exploit to my replace-by-fee toolkit(1) for at least another week or so
> though - pull-reqs accepted.
>
> 1) https://github.com/petertodd/replace-by-fee-tools
Do you have or can you provide a version compatible with CPFP, such that a
child paying a higher fee trumps the parent's replacement?
Preferably something that will merge cleanly into 0.9.x-ljr :)
Luke
next prev parent reply other threads:[~2014-09-28 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 2:02 [Bitcoin-development] SPV clients and relaying double spends 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
2014-09-28 5:15 ` [Bitcoin-development] replace-by-fee v0.9.3 release Peter Todd
2014-09-28 17:03 ` Luke Dashjr [this message]
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=201409281703.51377.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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