<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated></updated>
  <generator>https://nostr.ae</generator>

  <title>Nostr notes by </title>
  <author>
    <name></name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.ae/npub1auy2ject3577tjhee32hheheld29rs92jgeff4ulvclvwr96g5dsje0edv.rss" />
  <link href="https://nostr.ae/npub1auy2ject3577tjhee32hheheld29rs92jgeff4ulvclvwr96g5dsje0edv" />
  <id>https://nostr.ae/npub1auy2ject3577tjhee32hheheld29rs92jgeff4ulvclvwr96g5dsje0edv</id>
  <icon></icon>
  <logo></logo>




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

</feed>