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