<oembed><type>rich</type><version>1.0</version><author_name>npub1swfeusu3ua9trup00qcnrgc2yndksyvgku4epk5tec7u4fmrez6qxpul5t</author_name><author_url>https://nostr.ae/npub1swfeusu3ua9trup00qcnrgc2yndksyvgku4epk5tec7u4fmrez6qxpul5t</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-02-12&#xA;📝 Original message:&gt; To remain useful as border router, the replace-by-fee patched core should&#xA;&gt; only relay double spend if it actually replaces an earlier transaction, as&#xA;&gt; otherwise the replace logic that is according to your commit more than just&#xA;&gt; fee comparison, would have to be replicated in the proprietary stack and&#xA;&gt; mempool might get out of sync with that of the border router.&#xA;&gt;&#xA;&#xA;Why don&#39;t you use getrawmempool RPC call to synchronize mempool contents?&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150212/d898c0e1/attachment.html&gt;</html></oembed>