<oembed><type>rich</type><version>1.0</version><author_name>npub1auy2ject3577tjhee32hheheld29rs92jgeff4ulvclvwr96g5dsje0edv</author_name><author_url>https://nostr.ae/npub1auy2ject3577tjhee32hheheld29rs92jgeff4ulvclvwr96g5dsje0edv</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-12-27&#xA;📝 Original message:&#xA;I&#39;ve only really been getting my hands into LN the past few weeks but&#xA;I thought I&#39;d share my thoughts here.&#xA;&#xA;ZmnSCPxj via Lightning-dev &lt;lightning-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; Perhaps some day, in the LONG TERM, the limits may be increased&#xA;&#xA;I was always under the impression that the channel and payment limits&#xA;were intended to be training wheels, this is the first I&#39;ve heard of&#xA;them intended to stick around long term. I find the channel limit to&#xA;be particularly restrictive, as it hinders some use cases I&#39;d envision&#xA;where large payment channels between two parties are useful and can&#xA;also be used for routing LN payments. Large payments afaik can be&#xA;broken up into smaller ones without incurring too much cost or&#xA;trouble, but that&#39;s not the case for creating channels. As the channel&#xA;itself involves only two parties - and in sticking to my general&#xA;political/philosophical mantra - there is really no justification for&#xA;limits to be imposed on this. Which brings me to my next point.&#xA;&#xA;&gt; If I run a node which refuses the higher limits, then:&#xA;&gt;&#xA;&gt; 1. The alt-lightning network node cannot channel to me directly to unless&#xA;&gt; they accept my channel size limit. (they will have to channel through a node&#xA;&gt; that will accept my channel size limit and also accept their increased&#xA;&gt; channel size limit, or just never open a channel to me greater than&#xA;&gt; 167mBTC).&#xA;&#xA;The parenthetical here is correct. If nodes A and B have huge channels&#xA;between each other, they can still be totally compatible with the rest&#xA;of the network as long as they don&#39;t try exceeding the channel limit&#xA;with nodes that won&#39;t accept it. In practice, &#34;whales&#34; will quite&#xA;easily be able to run their own rules with regards to these limits and&#xA;I think that is a good thing.&#xA;&#xA;&gt; There is also again the wisdom, that one should keep most of the funds in&#xA;&gt; cold storage, and only a small amount for spending in hot wallets like&#xA;&gt; Lightning nodes&#xA;&#xA;I think this is a top-down way of thinking that runs counter to the&#xA;spirit of bitcoin. The &#34;wisest&#34; thing to do in fact may be to simply&#xA;buy inflation-adjusted treasury bonds and not mess with bitcoin at&#xA;all, much less the experimental lightning network. As advice this is&#xA;perfectly fine to share with others for them to follow on a voluntary&#xA;basis, but I don&#39;t see why this ought to be enforced as a rule on a&#xA;protocol level.&#xA;&#xA;Also, I personally can&#39;t see a reason why a node would reject a large&#xA;channel being made with it, where is the downside or risk? The party&#xA;committing funds to the channel is the one risking loss or delay of&#xA;funds.&#xA;&#xA;&gt; Yes.  Indeed to my knowledge no current LN software implements non-zero&#xA;&gt; push_msat&#xA;&#xA;As an aside, I believe push_sat is implemented by LND.&#xA;&#xA;Anyway, I think these limits are fine for LN&#39;s baby steps, but overly&#xA;restrictive for a mature LN network. Ideally I believe I&#39;d want these&#xA;limits to be non-existent or configurable by nodes (and announced to&#xA;peers), but maybe I am missing some technical reasons why such an&#xA;approach would be challenging. Either way I expect I&#39;ll be among the&#xA;first to run software with less restrictive limits when LN&#39;s training&#xA;wheels are ready to come off.&#xA;&#xA;Thanks for the discussion and for your work on LN.&#xA;&#xA;Daniel</html></oembed>