<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-19&#xA;📝 Original message:&#xA;There could be some corners where the incentives may not work out 100%, but&#xA;I doubt that any routing node would bother exploiting this. Especially&#xA;because there could always be that reputation scheme at the sender side&#xA;which may cost the routing node a lot more in lost routing fees than the&#xA;marginal gain from the upfront payment.&#xA;&#xA;Another option is that nodes that don&#39;t care to be secretive about their&#xA;channel balances could include the actual balance in a probe failed&#xA;message. Related: https://github.com/lightningnetwork/lightning-rfc/pull/695&#xA;&#xA;Overall it seems that htlc-less probes are an improvement to what we&#xA;currently have. Immediate advantages include a reduction of the load on&#xA;nodes by cutting out the channel update machinery, better ux (faster&#xA;probes) and no locked up liquidity. On the longer term it opens up the&#xA;option to charge for failed payments so that we finally have an answer to&#xA;channel jamming.&#xA;&#xA;ZmnSCPxj, as first person to propose the idea (I think?), would you be&#xA;interested in opening a draft PR on the spec repository that outlines the&#xA;new message(s) that we&#39;d need and continue detailing from there?&#xA;&#xA;Joost&#xA;&#xA;On Sat, Oct 16, 2021 at 12:51 AM ZmnSCPxj via Lightning-dev &lt;&#xA;lightning-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt; Good morning Owen,&#xA;&gt;&#xA;&gt; &gt; C now notes that B is lying, but is faced with the dilemma:&#xA;&gt; &gt;&#xA;&gt; &gt; &#34;I could either say &#39;no&#39; because I can plainly see that B is lying, or&#xA;&gt; &gt; I could say &#39;yes&#39; and get some free sats from the failed payment (or&#xA;&gt; &gt; via the hope of a successful payment from a capacity increase in the&#xA;&gt; &gt; intervening milliseconds).&#34;&#xA;&gt;&#xA;&gt; Note that if B cannot forward an HTLC to C later, then C cannot have a&#xA;&gt; failed payment and thus cannot earn any money from the upfront payment&#xA;&gt; scheme; thus, at least that part of the incentive is impossible.&#xA;&gt;&#xA;&gt; On the other hand, there is still a positive incentive for continuing the&#xA;&gt; lie --- later, maybe the capacity becomes OK and C could earn both the&#xA;&gt; upfront fee and the success fee.&#xA;&gt;&#xA;&gt; &gt; So C decides it&#39;s in his interest to keep the lie going. D, the payee,&#xA;&gt; &gt; can&#39;t tell that it&#39;s a lie when it reaches her.&#xA;&gt; &gt;&#xA;&gt; &gt; If C did want to tattle, it&#39;s important that he be able to do so in a&#xA;&gt; &gt; way that blames B instead of himself, otherwise payers will assume&#xA;&gt; &gt; (incorrectly, and to C&#39;s detriment) that the liquidity deficit is with C&#xA;&gt; &gt; rather than B.&#xA;&gt;&#xA;&gt; That is certainly quite possible to do.&#xA;&gt;&#xA;&gt; Regards,&#xA;&gt; ZmnSCPxj&#xA;&gt; _______________________________________________&#xA;&gt; Lightning-dev mailing list&#xA;&gt; Lightning-dev at lists.linuxfoundation.org&#xA;&gt; https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211019/dd316d31/attachment.html&gt;</html></oembed>