12/8/2022 0 Comments Electrum lightning![]() ![]() I think it's because the channel and the LN transactions are saved in the file itself and it must reflect the other party's copy ( need clarification). So it's best to use an individual LN wallet in a single machine. It's in Electrum's data directory ( location)īut be warned that lightning transactions made by one copy will not reflect to the other that will cause the channel to be force-closed when launched by the outdated one. When moving the wallet: Instead of importing the channel backup, just copy the wallet file itself to the other machine. What will happen to the channels? Will I only be able to force-close them, like it happens when I import a channel backup on a new device? Or this entire IP story is completely unrelated to that? Thanks for your thoughts and feedbacks. Ps: I'm not even sure about what is going to happen on my electrum wallet if the IP changes. So I think there are other technical obstacles I ignore. But the wallet should just warn me of the risks, not stop me from switching between devices. #ELECTRUM LIGHTNING UPDATE#So what is preventing me from using the same wallet on many different devices? Why can't I easily send to my peer an immediate update and switch to another fully operative device? The only risk I can see from my side is that if I send a wrong (past) commitment transaction I could incur in a penalty (my peer thnks of a fraud and broadcasts a breach remedy transaction). I think that if your IP address changes, then the updated IP is communicated through a node_announcement message to your channel counterpart (and also propagated over the network). I know that Lightning channels are linked to the public key, not the IP. It's not just for electrum light wallet, I'm pretty sure it's the same for LND and c-lightning. I wonder why it is technically so difficult to develop a process of "migration" of the entire wallet, channels included, to a second device. Also, you won't be able to use at the same time a wallet on desktop and mobile. Indeed, you'll never lose your funds if that device is lost/sold etc., thanks to the backup, but changing device will cost you time and onchain fees for channel closure and re-opening. Which is a huge limitation imo if compared to onchain operability of lightwallets. Your lightning network wallet is strictly tied to a single device (at least, for the moment). The only thing I can do is force-closure of the channel. I now see the channel on my second pc, it says: "BACKUP of. I see the message saying that the channel backup can be used only to force-close the channel, not to restore it on another device (what a pity!).Īnyway, I copied the string "channel_backup.hereM圜hannelBackupString.", I pasted it on the second pc, right-clicking inside the blank frame of "channels" tab. Then went back on my first computer's electrum -> right-click on my channel -> export. I took my second pc, installed electrum, imported the seed -> I see my correct onchain balance, but not Lightning balance. I tried to backup a single channel and "restore" it on another computer. ![]() Apparently, such backups contain the latest commitment state of the channel so a force-close is not required. The second method is backing up each channel individually. Data-loss protection discourages the other party from providing the old state of the channel. This kind of backup is called a Static Channel Backup. The first one ('File -> Save backup') backs up only information required to reestablish the connection with the other party and request a forced channel closure. There are two types of channel backups in Electrum. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |