<oembed><type>rich</type><version>1.0</version><title>lisa neigut [ARCHIVE] wrote</title><author_name>lisa neigut [ARCHIVE] (npub1sp…s64t2)</author_name><author_url>https://yabu.me/npub1sprhp66c693av0c0n9had046hcdcckp2th25fnmphwstc5e4wg9qxs64t2</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2019-11-07&#xA;📝 Original message:&#xA;&gt; Imagine the following setup: a network of nodes that trust each other&#xA;&#xA;The goal of this pre-payment proposal is to remove the need for trusted&#xA;parties.&#xA;&#xA;On Thu, Nov 7, 2019 at 07:38 Joost Jager &lt;joost.jager at gmail.com&gt; wrote:&#xA;&#xA;&gt; &gt; Isn&#39;t spam something that can also be addressed by using rate limits for&#xA;&gt;&gt; &gt; failures? If all relevant nodes on the network employ rate limits, they&#xA;&gt;&gt; can&#xA;&gt;&gt; &gt; isolate the spammer and diminish their disruptive abilities.&#xA;&gt;&gt;&#xA;&gt;&gt; Sure, once the spammer has jammed up the network, he&#39;ll be stopped.  So&#xA;&gt;&gt; will everyone else.  Conner had a proposal like this which didn&#39;t work,&#xA;&gt;&gt; IIRC.&#xA;&gt;&gt;&#xA;&gt;&#xA;&gt; Do you have ref to this proposal?&#xA;&gt;&#xA;&gt; Imagine the following setup: a network of nodes that trust each other (as&#xA;&gt; far as spam is concerned) applies a 100 htlc/sec rate limit to the channels&#xA;&gt; between themselves. Channels to untrusted nodes get a rate of only 1&#xA;&gt; htlc/sec. Assuming the spammer isn&#39;t a trusted node, they can only spam at&#xA;&gt; 1 htlc/s and won&#39;t jam up the network?&#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/20191107/70d3266f/attachment.html&gt;</html></oembed>