<oembed><type>rich</type><version>1.0</version><author_name>npub18plyg5mfmzwlvkcx0fhudfll3x5phjvvlglw4dgj6t5ehyp87ttqzv2ml4</author_name><author_url>https://nostr.ae/npub18plyg5mfmzwlvkcx0fhudfll3x5phjvvlglw4dgj6t5ehyp87ttqzv2ml4</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-19&#xA;📝 Original message:Great. Thank you for this!&#xA;&#xA;Adrian&#xA;&#xA;On Fri, Jun 19, 2015 at 7:40 AM, Chun Wang &lt;1240902 at gmail.com&gt; wrote:&#xA;&#xA;&gt; On Fri, Jun 19, 2015 at 10:00 PM, Adrian Macneil &lt;adrian at coinbase.com&gt;&#xA;&gt; wrote:&#xA;&gt; &gt; However, we do rely pretty heavily on zeroconf transactions for merchant&#xA;&gt; &gt; processing, so if any significant portion of the mining pools started&#xA;&gt; &gt; running your unsafe RBF patch, then we would probably need to look into&#xA;&gt; this&#xA;&gt; &gt; as a way to prevent fraud.&#xA;&gt;&#xA;&gt; This might be useful to you: https://www.f2pool.com/api/mempool&#xA;&gt;&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/d962d207/attachment.html&gt;</html></oembed>