{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-12-01\n📝 Original message:\u003e \"This payment did not become spendable since xxx minutes. Check with the\n\u003e sender if s/he paid the Bitcoin network fee. Check if your internet\n\u003e connection is working properly.\" (incoming)\n\nThat seems reasonable.\n\nThe other message should be implementable today, I think? If numBroadcastPeers \u003e 0 post 0.10.3 then you know the tx made it out to the internet.\n\nUnfortunately if nodes start to diverge a lot in terms of what they will accept, then “transmitted” is no longer a clean binary yes/no thing. Guess we’ll have to jump that hurdle when we come to it.\n\n\u003e Guess you're right. But as you said, we're not there yet.\n\nThe payment protocol at least would need some notion of fee, or possibly (better?) the ability for a recipient to specify some inputs as well as some outputs.\n\nOriginally I think we were hoping for child-pays-for-parent. I guess that needs someone to sit down and focus on it for a while, assuming we still think that’s a good idea.\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: smime.p7s\nType: application/pkcs7-signature\nSize: 4127 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131201/e59627ff/attachment.p7s\u003e"}