<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2025-10-27T22:47:50Z</updated>
  <generator>https://nostr.now</generator>

  <title>Nostr notes by LNBϟG</title>
  <author>
    <name>LNBϟG</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.now/npub1ngumlqmus6xkrmvvee4yc7swh9h4uk7vpq4ddt7a2jtvkc22y0asrse3pv.rss" />
  <link href="https://nostr.now/npub1ngumlqmus6xkrmvvee4yc7swh9h4uk7vpq4ddt7a2jtvkc22y0asrse3pv" />
  <id>https://nostr.now/npub1ngumlqmus6xkrmvvee4yc7swh9h4uk7vpq4ddt7a2jtvkc22y0asrse3pv</id>
  <icon>https://lnbig.com/nostr/LNBIG.png</icon>
  <logo>https://lnbig.com/nostr/LNBIG.png</logo>




  <entry>
    <id>https://nostr.now/nevent1qqsfmzqgcg445uuw4c2x2ge8khttr7rqegvz24yx5jy4ucw8qrknangzyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkldw5wk</id>
    
      <title type="html">The last 24 hours of #LNBiG (2025-05-27): Amount transactions: ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsfmzqgcg445uuw4c2x2ge8khttr7rqegvz24yx5jy4ucw8qrknangzyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkldw5wk" />
    <content type="html">
      The last 24 hours of #LNBiG (2025-05-27):&lt;br/&gt;Amount transactions: 5611&lt;br/&gt;The sum of transfered BTC: 47.08249757&lt;br/&gt;Percentile 0%: 1 sats&lt;br/&gt;Percentile 25%: 18247 sats&lt;br/&gt;Percentile 50%: 67440 sats&lt;br/&gt;Percentile 75%: 248209 sats&lt;br/&gt;Percentile 95%: 3421320 sats&lt;br/&gt;Last 24 hours fee earning: 1730456 sat (0.01730456 BTC)&lt;br/&gt;#LightningNetwork
    </content>
    <updated>2025-05-27T09:04:19Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsfjq45qu5d8tzjhz2kqtzsw49dn8tucyva2jat8trpxnlh4muqzjszyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lk2cp8s9</id>
    
      <title type="html">Hello everyone! I want to share my opinion on how much a node or ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsfjq45qu5d8tzjhz2kqtzsw49dn8tucyva2jat8trpxnlh4muqzjszyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lk2cp8s9" />
    <content type="html">
      Hello everyone! I want to share my opinion on how much a node or multiple nodes in the #Bitcoin #LightningNetwork can earn for their owners, using the example of my own nodes. I will provide the figures as an annual percentage.&lt;br/&gt;&lt;br/&gt;Currently, over approximately five days, the entire network of my nodes earns about 500,000 satoshis per day on average. This is an average parameter. 500,000 satoshis is 0.005 bitcoins.&lt;br/&gt;&lt;br/&gt;The liquidity on my side across all nodes is roughly around 300 bitcoins. So, let&amp;#39;s simply calculate the annual percentage. You can roughly calculate it like this: 0.005 bitcoin multiplied by 365 days divided by 300 bitcoins. Multiply by 100%, and it comes out to about 0.6% profit from fees, which are currently at 700 ppm &#43; 1 sat base fee.&lt;br/&gt;&lt;br/&gt;This formula does not take into account the costs for opening channels, which include on-chain fees for Bitcoin channel opening transactions, nor does it include various expenses related to channel closures, whether automatic or forced, cooperative or forced. We are just taking the net figure as if the same channels were open all year without any expenses. You should also consider the risks associated with annual node maintenance. These include hosting costs, creating backups, labor efforts, and the risks of node hacking, which could theoretically be hacked and have all funds stolen.&lt;br/&gt;&lt;br/&gt;Is this a profitable venture? You decide for yourselves. I just wanted to share some useful information with you.&lt;br/&gt;&lt;br/&gt;Goodbye!&lt;br/&gt;&lt;br/&gt;#Stats #LNBiG #profit #fees
    </content>
    <updated>2025-04-22T20:27:44Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqstn6xxa94qhuvqpnf8ywcw0rx4fp6gmvm648hwyjg0t9n8pk73xmqzyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkmlmfk8</id>
    
      <title type="html">As a result of all my thoughts and experiments, I&amp;#39;ve ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqstn6xxa94qhuvqpnf8ywcw0rx4fp6gmvm648hwyjg0t9n8pk73xmqzyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkmlmfk8" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsdjdr64tj23y6uhd8tf07wcxqs4zs2xauz38tjjljvnqxp6ewsx6sjdw557&#39;&gt;nevent1q…w557&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;As a result of all my thoughts and experiments, I&amp;#39;ve concluded that I can&amp;#39;t find any optimal way to effectively earn money and maintain a high flow. It turns out that when you increase the commission, at some point the number of transactions drops significantly, but you earn more, and this happens not regularly but in bursts. It&amp;#39;s very difficult to determine where you&amp;#39;re right and where you&amp;#39;re not. Therefore, I got fed up with all of this, abandoned it, and set fixed commissions on the channels. Initially, I set them to zero entirely, and the flow increased significantly. Now, if memory serves me right, my commission is 10 ppm, and about the same flow is occurring as when commissions were completely zero, but now I&amp;#39;m earning around $5-10 per day. It&amp;#39;s possible to earn more, of course, but I just got tired of constantly changing the code and adjusting commissions.&lt;br/&gt;&lt;br/&gt;Of course, when talking about earnings, it&amp;#39;s important to keep in mind that I&amp;#39;m simply taking the numbers from the commissions. But you have to consider that every day some channels close randomly or at the request of the remote party, some channels get severed due to protocol mismatches with the remote side, or sometimes I open channels to nodes with which I don&amp;#39;t have existing channels, and satoshis are also spent on that. So it seems like all earnings are being consumed.&lt;br/&gt;&lt;br/&gt;But there&amp;#39;s an interesting point. As you know, you can buy a channel on my website, and that server, LND, which manages it, has been showing me over the past few years that, in total, more than one Bitcoin has been accumulated from all the payments for opening channels. I keep track of these statistics; I don&amp;#39;t have the data on hand right now, but it&amp;#39;s roughly around one and a half Bitcoin earned already. This includes the amount I&amp;#39;m trying to cover for opening and future closing of channels, as well as the percentage I set in my source code based on the size of the channel.&lt;br/&gt;&lt;br/&gt;So, in principle, you can probably earn money, perhaps by selling channel capacity rather than earning from commissions. Moreover, you have to consider that over the entire time my network has been running, which is about six and a half years, the difference between what I can get back when closing all channels and what I put into the system shows that I&amp;#39;ve lost approximately 3.3 Bitcoin. This includes several instances where my nodes were penalized and all funds were confiscated. There were also moments when there was a bug in the LND server, and breaches occurred. If memory serves, this amounts to about 0.8 Bitcoin in total. The rest consists of funds spent on commissions, opening, and subsequently closing cooperative or force-closed channels, which I was very actively opening in the beginning.
    </content>
    <updated>2025-03-15T00:26:04Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsdjdr64tj23y6uhd8tf07wcxqs4zs2xauz38tjjljvnqxp6ewsx6szyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkjt6z46</id>
    
      <title type="html">Simple example. Previously, I tried to balance channels using ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsdjdr64tj23y6uhd8tf07wcxqs4zs2xauz38tjjljvnqxp6ewsx6szyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkjt6z46" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqs9awdrwhluqtpn3ghr649kjeyu0nly3njt4taw7fdhu4sxzf6x9xc8hj8e8&#39;&gt;nevent1q…j8e8&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Simple example. Previously, I tried to balance channels using fees. I had an algorithm where if a large portion of the channel&amp;#39;s funds was on my side, I set fees low until the balance shifted more toward the remote side. Once, I encountered a situation where I couldn’t send a payment to a seller through my nodes. I investigated and found that my wallet was receiving an error stating that the fee on one of my nodes didn’t match the fee the wallet obtained from the network graph. In other words, the node had a higher fee than what my wallet had in its data. I continued to investigate and discovered that the node had raised the fee several hours ago and reported it to the network via the Gossip protocol, but my wallet, which was always connected to the network at that time, did not receive this update and still had the old information.&lt;br/&gt;&lt;br/&gt;I don’t remember all the exact details of that case now. I know that in the packet returned to the sender in case of an error, the new fees present on the node at that moment are included. But for some reason, my wallet didn’t set the new fee and didn’t resend through that node. I don’t recall why that happened. However, while studying that case, I concluded that balancing channels using fees has significant drawbacks because the fee percentage changes over time, causing many payments that could have gone through to fail. Subsequently, I at some point made the fees on channels fixed.&lt;br/&gt;&lt;br/&gt;Later, after some time, I had the thought that balancing using fees probably has a logical flaw. Because when we have a large balance on our side, effectively locking up a large portion of our funds, logic suggests that this is an ideal scenario to earn fees. But channel balancing pushes us to use minimal fees in such cases. And channel balancing also pushes us to raise fees when liquidity in the channel is running low. From a logical standpoint, I think it should be the opposite. From a profitability standpoint, that is. A node should earn fees specifically when it has a balance in the channel and not earn them when it doesn’t.
    </content>
    <updated>2025-03-15T00:15:36Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqs9awdrwhluqtpn3ghr649kjeyu0nly3njt4taw7fdhu4sxzf6x9xczyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lk78spyd</id>
    
      <title type="html">Yes, the 95th percentile means that only 5% exceed the specified ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqs9awdrwhluqtpn3ghr649kjeyu0nly3njt4taw7fdhu4sxzf6x9xczyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lk78spyd" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqs9xaedxhj4s50q0tkr604hfzh7nrzexnf2lylwdsslcnkark6p2xqhdpkpt&#39;&gt;nevent1q…pkpt&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Yes, the 95th percentile means that only 5% exceed the specified size, but day by day this figure fluctuates. Regarding fee optimization, I tried manually setting fees on all channels to approximately 800 ppm, and then progressively, over many days, lowering them and manually recording the number of successful payments, the total payment amounts, and so on in a spreadsheet. When you look at the results over a short period, it seems like you&amp;#39;ve found some optimal fee, but as more time passes, you realize that all these fluctuations have some other internal nature.&lt;br/&gt;&lt;br/&gt;I tried to think about how optimization could be done, but it seems to me that this task is impossible because full optimization would require knowing the complete network graph with all node balances, which is fundamentally impossible. Moreover, this situation is constantly changing. Without knowing the balances of all nodes at a given moment, it&amp;#39;s impossible to accurately predict which node will be optimal at any given time, which fee will be optimal, and so on.&lt;br/&gt;&lt;br/&gt;Furthermore, payment paths and fees are set by the sender. The sender draws their information from the network graph, which always differs for each observer due to the slow propagation of gossip information.
    </content>
    <updated>2025-03-15T00:05:28Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsvnqtanjrfgntnwsfw685nc70f54cw45v5qvrz773qrn4mtyr6jyszyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lksjukxr</id>
    
      <title type="html">The last 24 hours of #LNBiG #Stats: Amount transactions: 31291 ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsvnqtanjrfgntnwsfw685nc70f54cw45v5qvrz773qrn4mtyr6jyszyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lksjukxr" />
    <content type="html">
      The last 24 hours of #LNBiG #Stats:&lt;br/&gt;Amount transactions: 31291&lt;br/&gt;The sum of transfered BTC: 16.04263519&lt;br/&gt;Percentile 0%: 1 sats&lt;br/&gt;Percentile 25%: 56 sats&lt;br/&gt;Percentile 50%: 848 sats&lt;br/&gt;Percentile 75%: 12320 sats&lt;br/&gt;Percentile 95%: 173687 sats&lt;br/&gt;Last 24 hours fee earning: 9582 sat (0.00009582 BTC)&lt;br/&gt;#LightningNetwork&lt;br/&gt;
    </content>
    <updated>2025-03-09T00:07:33Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsxvfj39lnwvdgadgqa74fnne70tnu4a8kd0eema6yrdm8fp4x9rsczyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkar7ldz</id>
    
      <title type="html">I have a feeling that the node &amp;#34;c=&amp;#34; is experiencing some ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsxvfj39lnwvdgadgqa74fnne70tnu4a8kd0eema6yrdm8fp4x9rsczyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkar7ldz" />
    <content type="html">
      I have a feeling that the node &amp;#34;c=&amp;#34; is experiencing some issues. The thing is, I&amp;#39;ve noticed that its capacity has decreased over the past few days. You can verify this yourself using the viewer at amboss.space. Another indirect sign of problems is that when I tried to cooperatively close channels with it a few minutes ago—channels that haven&amp;#39;t been used for payments in 14 days—several channels were unable to be closed cooperatively, even though the node is online. This usually happens when a node has lost data about the channels. The node itself is online, but when a remote peer connects to it and requests, for example, to cooperatively close a channel that was with it, the node doesn&amp;#39;t respond because it no longer has data about the channel. With this node, I have the feeling that this exact problem is occurring. It would be interesting to know from the owners of this node whether they are indeed experiencing any problems currently, whether they&amp;#39;ve had a failure or not. I think they have. #LightningNetwork
    </content>
    <updated>2025-03-09T00:04:55Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqs8umvtx2lfqrs8zhrmpgjzr7j9wwsluu63rua7c9mes6s7p8k5q5czyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkqw086u</id>
    
      <title type="html">The **third change** is that outgoing paid channels are opened ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqs8umvtx2lfqrs8zhrmpgjzr7j9wwsluu63rua7c9mes6s7p8k5q5czyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkqw086u" />
    <content type="html">
      The **third change** is that outgoing paid channels are opened with a mandatory requirement to support anchor channels from your side!&lt;br/&gt;&lt;br/&gt;For most, this change will go unnoticed, but for the owners of the old lightning nodes software, this means that they will not be able to open a paid channel outgoing to them from the LNBiG network (of course, funds for payment will not be taken thanks to the HODL invoice).&lt;br/&gt;&lt;br/&gt;I have to do this for the reason that in the current situation it is very dangerous to have channels without anchor support. Such channels are difficult to close if the bitcoin network fee market is growing and remains with a high fees for a very long time.&lt;br/&gt;&lt;br/&gt;#LightningNetwork #LNBiG #News&lt;br/&gt;&lt;blockquote class=&#34;border-l-05rem border-l-strongpink border-solid&#34;&gt;&lt;div class=&#34;-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2&#34;&gt;quoting &lt;br/&gt;&lt;span itemprop=&#34;mentions&#34; itemscope itemtype=&#34;https://schema.org/Article&#34;&gt;&lt;a itemprop=&#34;url&#34; href=&#34;/nevent1qqsdzh8e5r9vgklhu9t9fhmq4a432cvw8rx6akscgun3w9347m62aegppemhxue69uhkummn9ekx7mp0wj7fdw&#34; class=&#34;bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1&#34;&gt;nevent1q…7fdw&lt;/a&gt;&lt;/span&gt; &lt;/div&gt; The other good #news is that the #Tor v3 network is already configured on [those seven nodes](&lt;a href=&#34;https://lnbig.com/#/our-nodes&#34;&gt;https://lnbig.com/#/our-nodes&lt;/a&gt;) that will continue to work.&lt;br/&gt;&lt;br/&gt;Each of the seven nodes has an IPv4 and Tor address. #IPv6 I will add later. This means that you can open channels from the Tor network to these nodes. I also added the ability to open outgoing paid channels to nodes in the Tor v3 network (previously, this required a node from the Tor network to make a connection to the my node specified in the instructions for opening a paid channel). #LNBiG #LightningNetwork&lt;br/&gt;&lt;br/&gt;&lt;span itemprop=&#34;mentions&#34; itemscope itemtype=&#34;https://schema.org/Article&#34;&gt;&lt;a itemprop=&#34;url&#34; href=&#34;/nevent1qqsdpgn7c0updllwh6w7paxc2jwt59qrrsm442xh3vdu25jwfmpk50cppemhxue69uhkummn9ekx7mp074ar26&#34; class=&#34;bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1&#34;&gt;nevent1q…ar26&lt;/a&gt;&lt;/span&gt; &lt;/blockquote&gt;
    </content>
    <updated>2023-09-23T20:34:53Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsdzh8e5r9vgklhu9t9fhmq4a432cvw8rx6akscgun3w9347m62aegzyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkl249hs</id>
    
      <title type="html">The other good #news is that the #Tor v3 network is already ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsdzh8e5r9vgklhu9t9fhmq4a432cvw8rx6akscgun3w9347m62aegzyzdrn0ur0jrg6c0d3n8x5nr6p6uk7hjmesyz4440m42fdjmpfg3lkl249hs" />
    <content type="html">
      The other good #news is that the #Tor v3 network is already configured on [those seven nodes](&lt;a href=&#34;https://lnbig.com/#/our-nodes&#34;&gt;https://lnbig.com/#/our-nodes&lt;/a&gt;) that will continue to work.&lt;br/&gt;&lt;br/&gt;Each of the seven nodes has an IPv4 and Tor address. #IPv6 I will add later. This means that you can open channels from the Tor network to these nodes. I also added the ability to open outgoing paid channels to nodes in the Tor v3 network (previously, this required a node from the Tor network to make a connection to the my node specified in the instructions for opening a paid channel). #LNBiG #LightningNetwork&lt;br/&gt;&lt;blockquote class=&#34;border-l-05rem border-l-strongpink border-solid&#34;&gt;&lt;div class=&#34;-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2&#34;&gt;quoting &lt;br/&gt;&lt;span itemprop=&#34;mentions&#34; itemscope itemtype=&#34;https://schema.org/Article&#34;&gt;&lt;a itemprop=&#34;url&#34; href=&#34;/nevent1qqsdpgn7c0updllwh6w7paxc2jwt59qrrsm442xh3vdu25jwfmpk50cppemhxue69uhkummn9ekx7mp074ar26&#34; class=&#34;bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1&#34;&gt;nevent1q…ar26&lt;/a&gt;&lt;/span&gt; &lt;/div&gt; Hello everyone!&lt;br/&gt;&lt;br/&gt;There are some #news from [LNBiG](&lt;a href=&#34;https://lnbig.com/&#34;&gt;https://lnbig.com/&lt;/a&gt;):&lt;br/&gt;&lt;br/&gt;The number of nodes of the #LNBiG network will soon be reduced from 25 nodes to 7 ones. For more than a month, the opening of channels has been working only from/to 7 nodes. The list of active nodes is visible in the [&#34;Our nodes&#34;](&lt;a href=&#34;https://lnbig.com/#/our-nodes&#34;&gt;https://lnbig.com/#/our-nodes&lt;/a&gt;) section. #LightningNetwork &lt;/blockquote&gt;
    </content>
    <updated>2023-09-23T20:25:24Z</updated>
  </entry>

</feed>