<oembed><type>rich</type><version>1.0</version><author_name>npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8</author_name><author_url>https://nostr.ae/npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-02-12&#xA;📝 Original message:On Feb 12, 2015, at 9:49 AM, Peter Todd &lt;pete at petertodd.org&gt; wrote:&#xA;&gt; &#xA;&gt; How does my replace-by-fee patch *not* do that?&#xA;&#xA;Does it broadcast a double spend only if it IS replacing an earlier? If yes, I am fine with it.&#xA;&#xA;Tamas Blummer&#xA;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150212/a0014230/attachment.html&gt;&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 496 bytes&#xA;Desc: Message signed with OpenPGP using GPGMail&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150212/a0014230/attachment.sig&gt;</html></oembed>