The Bitcoin Lightning Network (LN) has emerged as a game-changing solution in the world of crypto, addressing the transaction count scalability limitations of the Bitcoin blockchain. This Layer 2 protocol enables faster, cheaper, and more efficient transactions, paving the way for mass adoption. In this blog post, I will explore the fascinating history of the LN, from its inception to its current state.
The Genesis: A Whitepaper in 2015
The story of the Bitcoin Lightning Network began in 2015, when Joseph Poon and Thaddeus Dryja started working on a whitepaper titled "The Bitcoin Lightning Network: Scalable Off-Chain Instant Payments." The paper proposed a novel Layer 2 solution that could overcome the inherent scalability limitations of the Bitcoin blockchain, enabling millions of transactions per second. The paper was published on January 14th, 2016.
Lightning White Paper
Early Development and Progress
Following the release of the whitepaper, several teams started working on implementing the LN concept, including Lightning Labs, Blockstream, and ACINQ. These developers built and refined the LN protocol, creating software implementations such as the Lightning Network Daemon (LND) written in the programming language Go, Core Lightning (CLN) written mostly in Go and partially in Python, and Eclair written in Scala.
The Lightning Network Testnet
In late 2016, Blockstream engineers Paul “Rusty” Russell and Dr. Christian Decker completed the first LN transaction successfully on the Bitcoin testnet, a parallel network used for testing purposes. The test was made using Blockstream’s lightning prototype software, lightningd 0.5. It was a digital purchase from a web-store. This milestone marked the beginning of extensive testing and experimentation, paving the way for the first mainnet LN transactions.
The Mainnet Launch and the First LN Transactions
The first Bitcoin mainnnet Lightning Network transaction was created by software developer Alex Bosworth of Lightning Labs. He paid Bitrefill over lightning to pay his phone bill. Bitrefill is an international online service that enables users top up their prepaid mobile phone plans and buy various gift cards for many other services and products with bitcoin.
The Lightning Torch and Growing Awareness
The Lightning Network gained widespread attention in early 2019, thanks to the Lightning Torch experiment. This social media campaign involved passing an incremental LN payment (the torch) between users, showcasing the LN's capabilities for fast and low-cost transactions. The Lightning Torch attracted participants from around the world, including prominent figures such as Twitter CEO Jack Dorsey, Litecoin founder Charlie Lee, Lightning Labs CEO Elizabeth Stark and Binance CEO Changpeng Zhao among many others.
The Growth of Infrastructure and Ecosystem
Over the years, the LN has experienced remarkable growth in terms of infrastructure, with an increasing number of nodes, channels, and network capacity. The development of user-friendly wallets like Zap, BlueWallet, and Phoenix has facilitated the adoption of LN payments, while services like Bitrefill and Fold have made it easier for users to spend their LN funds on everyday purchases. People also started running Bitcoin Lightning nodes at large numbers when Umbrel announced their easy to use node software that runs on low cost Raspi or on Linux computers.
LN Capacity Growth in BTC
Protocol Improvements and Enhancements
The LN continues to evolve, with developers working on protocol improvements such as multi-path payments, channel factories, and watchtowers (btw, check out our new Watch Swaps). In addition, the Bitcoin network's recent adoption of the Taproot upgrade, which includes the Schnorr signature algorithm, is expected to further enhance the efficiency and privacy of LN transactions.
Recent Adoption
By 2023, the Bitcoin Lightning Network has come a long way since its conception in 2015, transforming from an ambitious proposal to a functional, growing ecosystem. The LN received a massive boost from El Salvador where bitcoin is legal tender, and thus LN is used daily for LN payments in all kinds of establishments, including small local brands and large international brands like McDonald's and Starbucks. The social media platform Twitter introduced LN intergration through Strike a company that facilitates cross border payments using LN. Most recently the brand new decentralized social network Nostr started to support LN natively. As the LN continues to mature, it is poised to play a crucial role in driving the mass adoption of Bitcoin and revolutionizing the world of digital finance.
Operating a Bitcoin Lightning Network node can be a great way to contribute to the network and earn some extra income, but it also comes with some risks. In this blog post, we will discuss how to make your Lightning Network node safe to operate, including cyber security, power redundancy, and internet redundancy.
Cyber Security
Cyber security is a critical aspect of operating a Lightning Network node. A node that is not properly secured can be vulnerable to attacks that can result in the loss of funds or other sensitive information. Here are some tips to make your node cyber secure:
Choose a secure operating system The first step in securing your Lightning Network node is to choose a secure operating system. Linux is the recommended operating system for running a Lightning Network node, as it is more secure than other operating systems such as Windows or MacOS. Choose a version of Linux that is actively supported and updated, such as Ubuntu or Debian.
Secure your node's firewall A firewall is a network security system that monitors and controls incoming and outgoing network traffic. Configure your node's firewall to only allow incoming connections from trusted sources, such as your own IP address or known peers.
Install a VPN A VPN (Virtual Private Network) is a tool that encrypts your internet traffic and hides your IP address. By using a VPN, you can add an extra layer of security to your Lightning Network node. Only allow connections from trusted VPNs to your node.
Update regularly Keeping your node's software up-to-date is important for protecting it from vulnerabilities. Enable automatic updates for your operating system and be up to date on your LN implementation.
Protect your private keys Private keys are the most sensitive piece of information when it comes to securing your Lightning Network node. It's crucial to keep your private keys offline and in a secure location, such as a hardware wallet. Make sure to backup your private keys in multiple locations. The same precautions should be used when generating a macaroon.
Use a secure password Choose a strong and unique password for your node. Use a combination of uppercase and lowercase letters, numbers, and symbols. Avoid using common words or phrases.
Enable two-factor authentication (2FA) Two-factor authentication (2FA) adds an extra layer of security to your LN node. If available (ex. on Umbrel) use a hardware wallet or an authenticator app such as Google Authenticator to enable 2FA.
Now, let's look at specific software recommendations for securing your Lightning Network node:
Use the LND Watchtower service, which monitors the blockchain for attempted breaches of your Lightning Network channels. Check out the Watch Swaps we offer on LN+ for LND nodes that have a built in watchtower service.
Use the LND Tor hidden service to add an extra layer of privacy to your node's network traffic.
Enable LND's "disable admin macaroon" option to prevent unauthorized access to your node's administrative API.
Consider synchronous database replication with LND/postgres.
Use the CLN Watchtower service, which monitors the blockchain for attempted breaches of your Lightning Network channels. On LN+ we offer Watch Swaps for CLN nodes that use The Eye of Satoshi service.
Use the CLN Tor hidden service to add an extra layer of privacy to your node's network traffic.
Enable CLN's "disable admin cookie" option to prevent unauthorized access to your node's administrative API.
Consider sqlite db mirroring network drives to reduce the chance of state data loss.
Power Redundancy
Power outages can happen anytime, anywhere. It is crucial to ensure that your Lightning Network node remains operational during a power outage. Here are some tips to achieve power redundancy:
Use an uninterruptible power supply (UPS): A UPS is a battery backup system that provides power to your Lightning Network node during a power outage. A UPS can keep your node operational for several hours, depending on its capacity.
Use a generator: If you live in an area where power outages are frequent, consider using a generator as a backup power source for your Lightning Network node.
Avoid using Wi-Fi: A wired internet connection is more reliable than a Wi-Fi connection during a power outage.
Internet Redundancy
A reliable internet connection is also essential for operating a Lightning Network node. Here are some tips to ensure internet redundancy:
Use a wired internet connection: A wired internet connection is more reliable than a wireless connection. If possible, use a wired connection to connect your Lightning Network node to the internet.
Use a backup internet connection: If your primary internet connection goes down, a backup internet connection can keep your node operational. Consider using a mobile hotspot or a secondary wired connection as a backup.
In conclusion, operating a Lightning Network node can be a great way to contribute to the network and earn some extra income. However, it is essential to ensure that your node is safe to operate. By following the tips discussed in this blog post, you can make your Lightning Network node cyber secure and ensure power and internet redundancy, making it more resilient to power and internet outages.
TL;DR; I'm introducing Watch Swaps, a service similar to the Liquidity Swaps, but instead of opening channels to each other, node operators will watch each other's nodes with their watchtower services to protect against malicious channel force closure attacks, and the resulting potential loss of funds.
LN+'s first feature, the Liquidity Swaps have been very successful in the last year or so. More than 12K liquidity swaps allowed Bitcoin lightning network node users to cooperate with each other and open 40K channels in a mutually beneficial and efficient way. Liquidity swaps weren't only beneficial to individual node operators but to the network as a whole as well, because together we managed to decentralize the network. LN became highly resilient to single large nodes dropping out or behaving in an unfriendly way. A good test for this was when recently the second largest node (zerofeerouting) in the network dropped out. There was virtually no interruption to payments thanks to the many other nodes and their channels that could be used to route around the missing node.
Watch Swaps
Today, LN+ is launching a new feature that will hopefully improve another aspect of the network: security of your funds. We do this with the help of watchtowers to keep your channels safe even when your node is offline.
LN watchtowers are nothing new to LN+. We've been running an altruistic watchtower for a long time with the help of Voltage.cloud, but the reality is that this is a centralized solution and it's challenging to keep the server running smooth due to the huge demand.
The new LN+ Watch Swaps will allow node operators to find each other so they can watch each other's nodes using their watchtower services. With this setup, without a centralized watchtower service, even if your node is offline and somebody attacks one of your channels, the watchtower service of your choosing that nobody knows about will act on your behalf and issue a punish transaction that will send the entire capacity of the channel to your node.
Network Benefits
Besides the obvious benefit to individual nodes, running many watchtowers is beneficial to the entire network as a whole as well. When watchtowers are common, it becomes highly risky for an attacker to maliciously force close on a channel. Due to game theory, even nodes that have no watchtowers will be safe. There will be less attacks, which in turn helps the reputation of LN in general.
How Does it Work?
Watch Swaps are rather simple. It's an agreement between two participants: the author, who starts the watch swap, and the applicant, who applies to the watch swap.
The author can start a watch swap and setup the rules, such as type of watchtower (LND Watchtower or The Eye of Satoshi for CLN), the duration, and other unique rules they may have. The size of the watch swap is set automatically based on the author's node's size expessed as an LN+ rank.
As a side node, if you notice your LN+ node rank dropping a bit, that's nothing personal against you. It's expected across the board for many nodes starting now. It's a result of a new formula to calculate the rank, which hopes to help estimate the load a certain node will exert on the peer's watchtower service, so the pairing of nodes within a watch swap service is more fair and sustainable. Small nodes will be paired up with small nodes, and larger ones with larger ones. There are five watch swap sizes: Extra Small, Small, Medium, Large and Extra Large.
Applicants can look through the created watch swaps that match their node's size. Non-matching watch swaps will be filtered out from the view. The applicant can apply to the watch swap, but the application is not automatically accepted. The author can accept or reject the application. The reason for this extra approval step is necessary because watching each other node requires some level of trust. Both the applicant and the author will have a chance to assess each other's through their node profile information. If the application gets rejected, the applicant should not get offended, just apply elsewhere or create a watch swap themselves. Once an application is accepted, both parties will be able to see the URI for their peer's watchtower services, so they can add the service to their nodes.
Your watchtower service URI is kept secret from every party until the application is accepted. Once accepted the URI will be shared with your watch swap partner, and nobody else. In general, remember not to share your own or your watch swap partner's watchtower service URI with anyone else, or they may be able to connect to the service uninvited.
All this may feel complex just by reading about it in theory, but LN+ will guide you through the process step by step so it's easy for you in practice.
What's Next?
Before you create a watch swap, please do learn about the following subjects:
The concept of watchtowers in general and how your specific lightning implementation handles it. LND has a built in watchtower. On Umbrel the settings are exposed under Advanced Settings in your Lightning app (LND). For CLN you need a separate software The Eye of Satoshi (TEOS) to run a watchtower service, and there is a plugin for CLN to connect it.
How to enable the watchtower service on LND or how to install The Eye of Satoshi for CLN.
Creating your watchtower service URl. This is different from your URI to open channels.
Implications of running a watchtower service. It does require some resources on your part to run it (disk space, processing, bandwidth). Be conservative giving away your watchtower service URI.
Once you're knowledgeable about watchtowers and have the service URI ready, go ahead and start a watch swap or apply to an existing one.
Please do test out watch swaps and let me know if you see any issues, so I can fix them ASAP. Any ideas, recommendations are welcome!
Frequently Asked Question: Do I have to close my bitcoin lightning channels after some time?
Answer: No, you can keep channels open indefinitely. Many channels on the network are years old, and still working perfectly fine. There are 6 special situations when you want to close a channel listed below.
1. You absolutely NEED sats that are on your channel on chain instead. Examples for why:
The Bitcoin price went 10x, thus you want to put sats in cold storage.
You have to pay somebody on-chain.
2. Your peer went OFFLINE for a long time (9+ days), thus the channel is useless to receive or send. Also, if you both go offline, you may not be able to recover the sats in the channel. Don't be too hasty closing inactive channels, sometimes it takes a few days to fix a node.
3. You accumulated too many channels over time (100+), and your node is struggling to process all the traffic. This can happen on weaker hardware. Reducing channels fixes the problem.
4. You want to move your sats to a new node and you're not comfortable moving channel states files, or have no ability to do so. For example, when switching implementations (LND > CLN or vice versa).
5. You are going on a long sabbatical to a location without stable internet and/or electricity. Lightning nodes require to be online most of the time, unless you have a channel with a trusted node you agree with not to force-close you.
6. You're running a profit oriented routing node and a channel is not routing, but it is locking up funds (sats are on your side). Close and open to another node to make profit, unless you agreed to keep the channel open for a specific amount of time. You may also want to close & reopen to the same peer a larger channel if it was profitable.
If you can think of other reasons why you would want to close a bitcoin lightning network channel, please add a comment.
Read the interview I conducted with ZeroFeeRouting, a lightning network professional who ran one of the largest nodes in the bitcoin lightning network with immense success. The node was known for having no routing fees and instead earning an income by selling channels to other node operators for a small fee through their website.
LN+: Congratulations to your family regarding your second child. We wish you the very best health! Thank you for running your popular node, and for taking the time to answer these questions for the community. You ran a grand experiment in many ways and we would love to learn more about what you found out. My first question: How big was your node in terms of capacity, channel count and number of forwards (per month)? ZFR: I had about 100 BTC in capacity, a little more than 1,600 channels and about 450,000 forwards a month.
LN+: Did you prefer the LND or the CLN ecosystem overall? ZFR: I preferred the CLN ecosystem by a wide margin. It felt like the CLN developers are truly interested in supporting node operators and expanding the feature set of CLN. With lightning labs, I had the impression it was more about features they needed for their venture capital (Taro etc.). Might be a misjudgement - but that's how I felt.
LN+: Which implementation do you recommend for a hobby user and a serious profit oriented power user? ZFR: CLN.
LN+: Was your node abused in some way since it had no fees, such as excessive rebalancing or such? ZFR: It was certainly used for excessive rebalancing - would not call this abuse though. I have not been subject to any attacks.
LN+: Were you profitable, and how much did you earn (APR)? ZFR: The node was running profitably. My APY would clock in around 2% minus on-chain fees and hardware cost.
LN+: What was the most time consuming or stressful part of running a giant node? ZFR: Fund security.
LN+: For companies, do you recommend they run a single node or multiple nodes for redundancy? ZFR: One single node with backup in place.
LN+: What is missing in the lightning ecosystem? ZFR: I think it just needs a bit of time to mature.
LN+: What are the tools you use, you recommend the most? ZFR: I've not used any third party tools - besides BTCPay for my channel sales. Everything else were tools that I developed myself.
LN+: Do you have any secrets on which nodes are good to connect to? ZFR: Completely depends on the goal. For me it was always about connectivity. I wanted to be the best connected (i.e. least amount of hops) node in the network. If you just want to be able to make successful payments, ACINQ is the node to go. For routing, probably LOOP, WoS, Kraken, BFX as sinks and some good sources like Boltz. Breez also always worked like a source for me.
LN+: Do you have any strategies for node management that you wish to share to help people become more profitable? ZFR: Every node operator has their own strategy. It's crucial to be aware of the cost for rebalancing, otherwise you're just subsidizing other people's routing.
LN+: Do you expect the upcoming RGB and Taro protocols to increase lightning node profitability? ZFR: No.
LN+: If there was one thing you could change about the lightning protocol, what would it be? ZFR: It would be great if a wallet could "overpay" an invoice. Example: You break down a 10M payment into 15 x 1M chunks and send them out through different routes, as soon as 10M have been claimed by the target node, the target node can no longer claim the rest of the payments and they would return. This would reduce failed payments by a huge margin, because right now all payment parts have to succeed in order for the payment to succeed - in my example only two thirds would need to succeed. This is technically possible already but neither implemented nor specced.
LN+: Where do you get your lightning news from? ZFR: Twitter.
LN+: Which lightning wallets do you recommend for daily use? ZFR: I love Breez and OBW, because they give you full control. Phoenix is an excellent wallet if you don't want to think about anything. I've never used WalletOfSatoshi.
LN+: What was your largest cost during your experiment besides deployed BTC capital? ZFR: On-chain fees. I've had one force-close that cost me about 130,000 sats (30K for the force-close and another 100K for the sweeps).
LN+: Lightning is often compared to DeFi and criticised for having too little BTC deployed. What are your thoughts on this? ZFR: The only anology is that you can earn a return on locked up coins. But contrary to DeFi your locked up coins are actually used for something and the return is paid by participants of the network - not by issuing new tokens. I think the liquidity on the network matches market demand. Otherwise prices for liquidity would go up.
LN+: What is the biggest barrier for merchants to adopt lightning? ZFR: Same as BTC. The hassle of bookkeeping in what most tax authorities argue is a foreign currency.
LN+: Do you think Lightning can handle all the world’s transactions in the future or do we need L3 or other solutions? ZFR: It will be able to handle all the worlds transactions. Whether that will be 100% noncustodial I'm unsure.
LN+: Do you think there will be other zero fee nodes filling the gap you left open with your departure? ZFR: I don't know, but I am curious as well.
LN+: Can you recall any crisis or crazy story that happened during your experiment? ZFR: The disk containing my database crashed, back when I was running the node on a laptop. Luckily I was able to copy it to another drive - I had no other backups a t that time.
LN+: If you could give a single advice to a new node runner, what would that be? ZFR: Be aware that if you want to run at a profit, managing the node will take a lot of time.
LN+: What is something people care a lot about that they perhaps should not within the lightning ecosystem? ZFR: The way the network is working at the moment, is a hunt for cheap liquidity. If someone opens a channel to a sink node like LOOP and forgets to adjust the fee, the first one to snipe that liquidity (by using it to rebalance their own channel) wins. I wished this was not the case - but currently I don't see a way out of this.
LN+: Do you think geographically distributed nodes are important? ZFR: As long as there are tons of TOR only nodes being used as hops in routing (and speed is not a factor for wallets to construct) the routes it makes zero sense to set up geographically distributed nodes.
LN+: Tor is under attack, and it hurts lightning. What can we do about this in your opinion? ZFR: As hard as it sounds: Not use TOR for routing payments. There are options to run a node from home with a clearnet IP via VPN.
LN+: What are the important metrics we should follow regarding the lightning network in your opinion? ZFR: Total capacity in public channels, measured in USD.
LN+: How big do you think the lightning network will be at the same time next year, and in 5 years? ZFR: No idea. I would assume steady, exponential growth - at least 2x every year.
LN+: Is there any project or person that we should follow as it’s underappreciated? ZFR: I don't know if they're underappreciated but @fiatjaf, @callebtc as well as @jb55 are extremely strong recommendations.
LN+: If you hypothetically had 10,000 BTC, would you be able to deploy it to the lightning network successfully, and would it help the network? ZFR: Yes and yes. No idea about the potential yield though. Probably way less than 1 % at the current demand for LN liquidity.
LN+: Are you planning to come back as a professional node runner at one point? ZFR: Yes. I plan on doing this, if the opportunity presents itself.
LN+: Any other Bitcoin related project you’re following with great interest? ZFR: Nostr.
LN+: Do you know if it’s a boy or a girl? ZFR: A girl.
Lightning Network Plus (LN+), the free web app that helps lightning node operators to team up and create liquidity swaps to get free incoming liquidity, is now also available in the Umbrel app store.
There are several benefits to the offline Umbrel version of the app:
⚡️ Automatic Sign-in: No need to sign a message with Thunderhub or other apps
⚡️ Swaps Available for Me page: Easier to find swaps that match your node
⚡️ One-Click Channel Open: No need to copy paste node and channel capacity information
⚡️ Insufficient On-Chain Funds Detection: No more confusion around why the channel won't open
Swaps Index Page
The offline Umbrel app is meant to make it easier for new node operators getting started, therefore it offers all the basic required functionality (finding, joining and creating swaps, rating, comments, etc.) of the online version and some more. But, it doesn't offer all the features of the online version (ex. asking support questions, receiving and sending messages, creating posts, browsing node profiles, etc.). If you want to use all the features you can also sign-in with your node here. All your settings, and activity is synced between the offline and online versions.
Swap Details Page
If you're running an Umbrel node, I hope you will test out the app and enjoy the simpler experience. If you find any bugs, wish for a feature or have any trouble, let me know! Happy to help!
Today we are launching two highly requested minor feature updates, which will make it easier for you to sort through the available swaps on LN+.
Bookmarking UX
Bookmarking, as the name suggests, allows you to add a bookmark to a swap, so you can easily find it later by clicking the bookmark icon in the top right navigation or the bookmark button in your profile dashboard (as long as you're signed in.) If you bookmark a swap you will be notified if a new participant joins the swap. You would want to bookmark a swap if you're interested in the swap, but also want to wait and see which other participants are joining before committing. You can of course remove a bookmark if needed.
Hiding UX
Hiding is the opposite of bookmarking. It lets you hide a swap from all swap index pages. You would typically use hiding if you're confident that you are not interested in a swap, and you want to hide it from searches, so you can focus on the swaps you haven't reviewed yet. If you want to see the swaps you have hidden, click the Hidden button in your profile dashboard. You can unhide swaps if needed.
You can bookmark or hide a swap by clicking the relevant buttons on swap pages in the left sidebar below all the swap information.
As always, let me know if you notice any issues or if I can help you in any way.
An update for lightning network daemon (lnd) has been released that fixes a critical bug that was triggered by an unusually large transaction. This is the second time such a bug has surfaced within the last 2 weeks, but hopefully it's been now resolved for good thanks to the quick work by the btcd and lnd teams. 🙏
If you're running a managed node on Voltage.Cloud or with Umbrel, the services provide you with a one click update. Otherwise, you need to update yourself.
It's very important to update, otherwise your node will be stuck on Bitcoin block 761248. Without the update, funds in your channels may be at risk, and you will not be able to send, receive or route payments.
If you have a friend or collegue who doesn't attent to their node frequently, reach out to them and advise them to update as well.
Up untill now all liquidity swaps allowed both nodes with Clearnet and Tor connections (addresses) to join. This option will remain as is. However, we will now have two more options for special circumstances.
Now, you have the option to create swaps that only allow nodes with either Clearnet connection or only allow nodes with Tor connection.
Clearnet only swaps are beneficial to node operators who want to minimise the problems stemming from the slowness of the Tor network. I'm not entirely sure what the benefit of Tor only swaps are (privacy?), but they are here for you if ever needed.
On the swap index page, you can filter for All, Clearnet Only, and Tor Only swaps.
If your account is set to "Show Only Applicable" swaps, you will not even see the swaps that you can't apply to anyway based on the type of your available addresses. For example, if you only have a Tor address, you will not see Clearnet only swaps.
This new feature is exposed through our API as well.
As always, please let me know if you see any issues with this or any other feature on the site, or if I can help you with anything.
The version 2 of the API was launched a couple of month ago. In an effort to provide a full API to the community, I'm bringing version 2.1 with even more features as follows:
You can rate participants
You can get and update your account information
Get and clear notifications
Get node information including reputation scores
Some use cases for the LN+ API:
Upcoming full featured Umbrel app, so you can run your own install of LN+ in the privacy of your own server.
Automate your swap operations using a custom script of your own. For example, join a swap automatically when new channel capacity has been freed up because of recent channel closures.
Suggest relevant and useful swaps related to a given node, as some LN services and Telegram channels already do.
Pull reputation scores of a given node to improve the user experience on your LN service.
Pull the avatar, social image, twitter, website, and bio fields of a node on your LN service to make richer node profiles.
I'm happy to announce that a fully functional API for Lightning Network Plus has been released.
The objective of the API is to allow you to authenticate with your lighting node, request for existing swaps, create new swaps, apply to swaps, mark channels as opened, and post comments. Learn about all the details of the API.
Let me know if you need any fixes or improvements.
LN+ was started a year ago, and we celebrate this ocassion with an updated design for our swaps featuring neon lights enveloped in clouds.
The bitcoin ecosystem and especially the lightning network within it is growing fast, by any metric measured. I'm glad to be able to play a small role helping lightning network node operators collaborate and learn from each other. We're thankful for your support and encouragement.
