On Thu, Dec 21, 2023 at 09:59:04PM +, Antoine Riard wrote:
> Hi Peter,
>
> > Obviously a local replacement cache is a possibility. The whole point of
> my
> > email is to show that a local replacement cache isn't necessarily needed,
> as
> > any alturistic party can implement that cache for
Hi Peter,
> Obviously a local replacement cache is a possibility. The whole point of
my
> email is to show that a local replacement cache isn't necessarily needed,
as
> any alturistic party can implement that cache for all nodes.
Sure, note as soon as you start to introduce an altruistic party
On Fri, Dec 15, 2023 at 10:29:22PM +, Antoine Riard wrote:
> Hi Peter,
>
> > Altruistic third parties can partially mitigate replacement cycling(1)
> attacks
> > by simply rebroadcasting the replaced transactions once the replacement
> cycle
> > completes. Since the replaced transaction is in
Hi Peter,
> Altruistic third parties can partially mitigate replacement cycling(1)
attacks
> by simply rebroadcasting the replaced transactions once the replacement
cycle
> completes. Since the replaced transaction is in fact fully valid, and the
> "cost" of broadcasting it has been paid by the
While this seems like a reasonably obvious idea, I couldn't find a previous
example of it published on bitcoin-dev or elsewhere. So for the ability to cite
it, I'll publish it now.
# Summary
Altruistic third parties can partially mitigate replacement cycling(1) attacks
by simply rebroadcasting
