<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2013-12-01&#xA;📝 Original message:&gt; &#34;This payment did not become spendable since xxx minutes. Check with the&#xA;&gt; sender if s/he paid the Bitcoin network fee. Check if your internet&#xA;&gt; connection is working properly.&#34; (incoming)&#xA;&#xA;That seems reasonable.&#xA;&#xA;The other message should be implementable today, I think? If numBroadcastPeers &gt; 0 post 0.10.3 then you know the tx made it out to the internet.&#xA;&#xA;Unfortunately 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.&#xA;&#xA;&gt; Guess you&#39;re right. But as you said, we&#39;re not there yet.&#xA;&#xA;The 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.&#xA;&#xA;Originally 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.&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: smime.p7s&#xA;Type: application/pkcs7-signature&#xA;Size: 4127 bytes&#xA;Desc: not available&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131201/e59627ff/attachment.p7s&gt;</html></oembed>