You are not reading the latest stable version of this documentation. If you want up-to-date information, please have a look at 0.3.5.x.
The Lightning Network (LN) is a second ‘layer,’ built on top of the Bitcoin Protocol. As a result all transactions on LN are backed up by the full security of the Bitcoin network. Lightning is designed for instant payments between nodes, but similar to running a Bitcoin node, running your own is the only way to be sovereign. When you have your own node, you will have the convenience of linking a Lightning wallet, for use on the go. It is also possible to earn an income (granted a very small one at this time), if you are willing to learn how to become a ‘routing node.’
You can check out our “Using Lightning” video and learn the basics, including opening a channel with Start9.
Please remember to always open a “Private” channel with us, or your channel is likely to be closed. Please don’t hesitate to reach out to us with any questions.
A fee to close the channel (onchain) is set aside at opening.
The commitment fees are automatically negotiated every few blocks with your peer. They are on chain txs like all channel closes but they are not broadcast until you attempt to close the channel.
It is REALLY IMPORTANT to understand that if Lightning services are shut off for long periods of time (several days or more) it is possible for your peers to cheat you out of money. If you are not prepared to LOSE ALL THE MONEY IN YOUR CHANNELS, KEEP YOUR NODE RUNNING. That said, malicious actors on the network right now are probably sparse, and you may choose to only open channels with friends that may be a lot nicer to you if your node is not active.
Yes, the concept of a Watchtower was originally conceptualized in the LN whitepaper. A Watchtower is simply a lightning node to which you can give the authority to monitor transactions associated with your open payment channels.
Yes, you may run both. They will operate in their own environments and allow you to run services that depend on either.
Please see the Lightning Service Guides section for more details.
This is all on your Lightning node (LND or Core Lightning), including on-chain funds, while RTL (or Zap, Zeus, etc) is just a GUI for accessing your node.
LND backups are best done via StartOS’s backup flow, and this is the ONLY supported backup method. It is NOT supported to backup/restore from the seed. Everything crucial is backed up by our backup system, so you do not need the seed. The seed is ONLY for the onchain wallet and does NOT backup your channel state. That said, there was a high user demand to expose the LND Aezeed, and so, as of LND v0.16.4, this will be made available (on fresh installs only - as that is the only time Lightning Labs exposes this seed).
To clarify some of the reasons behind this issue:
First off, Lightning is fundamentally different than on-chain/Layer 1 (L1) Bitcoin. There is no way to compress all of that information down into a single 24 word seed in such a way that it will continue to work throughout your usage of the Lightning Network.
So, what is the LND seed for? In short, the seed is only used for the Layer1 portion of the funds you have locked up in LND. Due to the live nature of LND and lightning nodes in general, we tend to discourage keeping any significant amounts of money in the onchain portion of your wallet. Given that we cannot actually recover the Layer 2 (L2) funds with that seed, we needed to have a more holistic way to backup LND funds such that the backup would encompass the ability to get L2 funds back. The StartOS backup system does this, and this approach also happens to be a perfectly valid backup of your L1 funds as well. While Bitcoin users have been trained that the 24 word seed can be used to recover all of their funds, it is important to understand that lightning does not and cannot work this way. Exposing the seed gives you two separate things to keep track of in order to recover your funds instead of just one.
CLN/LND backups on StartOS consist of onchain funds and the set of channels. The node implementations (upstream) do not contain channel balances in the backup systems they use.
When you need to perform a recovery, it is important to understand all possible consequences. For most recoveries, such as a password reset, or hardware upgrade, there is no need to do a restore from backup. The preferred methods (explained here) are to “Attach” your existing data, or “Transfer” it.
If you do need to do a disaster recovery, your node reaches out to channel counterparties and requests that they force close the channel at the current balances. You are “trusting” them to report the correct balances. “Trusting” in quotes, because it would be very dangerous for them to try to cheat. They have no way of knowing that you are unaware of the true channel state. If they try to broadcast a revoked channel state, you could take all their money.
This is the current state of Lightning backups, and we will continue to stay at the forefront to help users protect their funds.
There are safe ways to do an “atomic move” of a LN node, but it requires a very specific sequence of actions and certain mistakes can result in your counterparties taking all your funds. Currently, LN works on a punishment scheme. This means if you publish revoked state, the counterparty is entitled to a claim on all the funds in the channel. This incentive system is what makes the whole system work. Without it, LN would be subject to various kinds of thievery.
The downside is that backups of old state are not safe. This is because your node might believe it is the real state of the channel, but it may be unaware of states created since then. The problem here is that your node naively believes something different from the truth, which can result in all of the funds being lost. In response to this reality, the safe backup systems, including those generated by RTL, actually do not include channel state. They only list the peers that you had channels with. Restoring these backups essentially politely asks your peers to force close the channels they have with you. In those moments it is possible for your peer to try and cheat you, but they cannot be 100% sure that you can’t punish them, so it’s extremely unlikely that they will attempt to do so.
We do not support this. Please see the above FAQ.
Check the LND logs, it can take a while to bootstrap, and starting RTL before this completes could cause errors.
Stop and Restart the Service.
You may need to restart the LND Service.
LND is waiting for Bitcoin to completely sync, and then needs to catch up on block scanning itself. This may take several minutes, and in some cases might require a restart of the LND service. Do this if the process takes more than 5-10 minutes.
It is possible to have lightning balances that are so low that they will not (or barely will) cover the on-chain fees to recoup into an on-chain wallet. If possible, move them to another Lightning node.