From: Matt Whitlock <bip@mattwhitlock.name>
To: Tom Harding <tomh@thinlink.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Can we penalize peers who relay rejected replacement txs?
Date: Thu, 09 Jul 2015 22:00:45 -0400 [thread overview]
Message-ID: <4333528.v2Hyrgt8Il@crushinator> (raw)
In-Reply-To: <559F2687.9080003@thinlink.com>
On Thursday, 9 July 2015, at 6:57 pm, Tom Harding wrote:
> Replace-by-anything can only work if conflicts are relayed, so the
> solution is not to act against the peer.
>
> Alex Morcos offered a suggestion on IRC -- track recently-rejected
> txid's and don't getdata them. The idea sounds good to me.
While that's probably a good idea, it wouldn't do much to reduce the load. I am not seeing many repeated transaction hashes among the "rejected replacement" messages in my log.
next prev parent reply other threads:[~2015-07-10 2:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 23:55 [bitcoin-dev] Can we penalize peers who relay rejected replacement txs? Matt Whitlock
[not found] ` <CADPq5bkyhdGocJncJfG5xkes6Qx-oHyeAsw0CUugqdqJZeubSQ@mail.gmail.com>
2015-07-10 1:36 ` Matt Whitlock
2015-07-10 1:57 ` Tom Harding
2015-07-10 2:00 ` Matt Whitlock [this message]
2015-07-10 0:42 Raystonn
2015-07-10 1:12 ` Matt Whitlock
2015-07-10 1:18 Raystonn
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=4333528.v2Hyrgt8Il@crushinator \
--to=bip@mattwhitlock.name \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=tomh@thinlink.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