<oembed><type>rich</type><version>1.0</version><author_name>npub1aslmpzentw224n3s6yccru4dq2qdlx7rfudfnqevfck637cjt6esswfqmx</author_name><author_url>https://nostr.ae/npub1aslmpzentw224n3s6yccru4dq2qdlx7rfudfnqevfck637cjt6esswfqmx</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2021-10-15&#xA;📝 Original message:&#xA;On Fri, Oct 15, 2021 at 4:21 PM Owen Gunden &lt;ogunden at phauna.org&gt; wrote:&#xA;&#xA;&gt; On Thu, Oct 14, 2021 at 09:48:27AM +0200, Joost Jager wrote:&#xA;&gt; &gt; So how would things work out with a combination of both of the&#xA;&gt; &gt; proposals described in this mail? First we make probing free (free as&#xA;&gt; &gt; in no liquidity locked up) and then we&#39;ll require senders to pay for&#xA;&gt; &gt; failed payment attempts too. Failed payment attempts after a&#xA;&gt; &gt; successful probe should be extremely rate, so doesn&#39;t this fix the ux&#xA;&gt; &gt; issue with upfront fees?&#xA;&gt;&#xA;&gt; Why couldn&#39;t a malicious routing node (or group of colluding routing&#xA;&gt; nodes) succeed the probe and then fail the payment in order to collect&#xA;&gt; the failed payment fee?&#xA;&gt;&#xA;&#xA;Yes they could, but senders should be really suspicious when this happens.&#xA;It could happen occasionally because balances may have shifted in between&#xA;probe and payment. But if it keeps happening they may want to ban this&#xA;routing node for a long time. This may disincentivize the routing node&#xA;enough to respond honestly to probes.&#xA;&#xA;Joost&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211015/a7713880/attachment.html&gt;</html></oembed>