Electrum Lightning Network walkthrough

[Rath_]

https://1ml.com/testnet/node/038863cf8ab91046230f561cd5b386cbff8309fa02e3f0c3ed161a3aeb64a643b9

I opened a channel to ion.radar.tech but it had been stuck in "REESTABLISHING" state for quite some time so I force-closed it and I will try opening a channel to some other node tomorrow.

[nc50lc]

What has happened with the swap feature? My channel's capacity has 0.049 tBTC, but I cannot receive anything. I'm trying to swap the lightning funds with on-chain funds to increase my receiving capacity, but it only allows me up to 0.002.
-snip-
Is this a bug? Is there any other way I can increase my receiving capacity in Electrum?

I think it's because the swap service provider (swap server) can only accept 0.002tBTC per swap:

• https://github.com/spesmilo/electrum/blob/master/electrum/submarine_swaps.py#L462
  
  

BTW, Boltz have a testnet swap but unfortunately, I haven't successfully sent lightning tBTC to it yet using channel connected to "endurance" (Electrum 'trampoline' channel for testnet).

• testnet.boltz.exchange | Select LN-BTC -> Bitcoin

[BlackHatCoiner]

Thank you, nc50lc! It worked. 

[eltNEG]

How can I disable trampoline routing while running electrum in daemon mode? I am running electrum on a server without a UI and I want to be able to connect to my btcpayserver lightening network.

[BlackHatCoiner]

How can I disable trampoline routing while running electrum in daemon mode? I am running electrum on a server without a UI and I want to be able to connect to my btcpayserver lightening network.

Go to Tools —> Preferences —> Lightning and uncheck the Trampoline usage. Restart electrum and now you'll be able to open a channel on any node you want.

Edit: Nevermind, read nc50lc's reply.

[nc50lc]

How can I disable trampoline routing while running electrum in daemon mode? -snip-

Use this command to disable "trampoline routing":

Code:

electrum setconfig -o use_gossip true

Alternatively, find the "config" file in your electrum data directory, edit it using a text editor, then insert this line:

Code:

"use_gossip": true,

Note: "true" because trampoline routing disables gossip.

[eltNEG]

How can I disable trampoline routing while running electrum in daemon mode? -snip-

Use this command to disable "trampoline routing":

Code:

electrum setconfig -o use_gossip true

Alternatively, find the "config" file in your electrum data directory, edit it using a text editor, then insert this line:

Code:

"use_gossip": true,

Note: "true" because trampoline routing disables gossip.

Thanks


More questions on electrum

1. Is there a notify function for lightenigng request created using electrum that works like the one for a normal address: `electrum notify <address> <callback url>`. I am currently using long pulling to get the status of a lightening request using the rhash and getrequest method.

2. Is there a way to hide some rpc functions like getseed? A walkaround that I am using is to build a proxy that validates the methods being called.

3. Is there a way for me to provide an inbound capacity from my btcpayserver to electrum?

I am sorry if my question is too much. I am trying to find a better way to add lightening to my website and the website of my clients

[moderator's note: consecutive posts merged]

[nc50lc]

By going though commands.py, I didn't find any command that fits those purpose.
https://github.com/spesmilo/electrum/blob/master/electrum/commands.py#L963-L966

For number 3, the alternative to sending some funds from Electrum to your btcpayserver is using "Reverse Swap".
https://github.com/spesmilo/electrum/blob/master/electrum/commands.py#L1230-L1232
But setting lightning_amount and onchain_amount will be tricky in the daemon because of the deductions: Boltz's service fee and the mining fee that they'll use for the on-chain return payment.

[Saterday_to_da_moon]

All the last channels I have opened in Electrum 4.1.5 recently got stuck on the 'OPENING' state (after more than 3 confirmations) and my LN payments are all failing. It was working fine the first 2 times I have use LN in Electrum.

When I checked the details of the channels, I can see this under Payments (HTPCs):

Fullfilled HTLCs
HTLC in current commitement transaction
Failed HTLCs

This issue is currently happening regardless if I'm using trampoline routing or not.

Any ideas why this is happening?

[Rath_]

Any ideas why this is happening?

Maybe it's a server related issue. Have you tried changing the server you are connected to a few times? Some implementations do not work well with the built-in Lightning Network functionality. You can also report your problem here if you still can't get it to work. You can also enable logging and share the logs with us.

[AhmedMSedeek]

Hello,

are there any plans of allowing public lightning channels on Electrum?, thus (thus enable charging payment routing fees)?

[nc50lc]

are there any plans of allowing public lightning channels on Electrum?, -snip-

As far as I can see in the repository, there's no discussion about enabling public channels in 'Issues' and 'Pull Requests'.

Filtered with "lightning" tag:

• github.com/spesmilo/electrum/issues
• github.com/spesmilo/electrum/pulls

You can ask the developers themselves or post a "pull-request wanted" topic in the 'Issues' tab.

[AhmedMSedeek]

As far as I can see in the repository, there's no discussion about enabling public channels in 'Issues' and 'Pull Requests'.

Filtered with "lightning" tag:

• github.com/spesmilo/electrum/issues
• github.com/spesmilo/electrum/pulls

You can ask the developers themselves or post a "pull-request wanted" topic in the 'Issues' tab.

Alright, Thanks a lot for your answer

[hero10]

Guys help. Trying to send via LN, not the first time.

The channel is open. There are enough limits. Last update.

But I get "mpp_timeout" and "transaction failed". What could be the reason?

[Rath_]

But I get "mpp_timeout" and "transaction failed". What could be the reason?

Since you used that channel in the past and it worked, it looks like some node in the selected routing path fails to route a part of your payment. If there was some other route available, your wallet would probably try it.

[nc50lc]

-snip-
But I get "mpp_timeout" and "transaction failed". What could be the reason?

I could also be your connection to the Lightning Network, Electrum takes time to fully connect if you're not using "Trampoline Routing" in the setting.
You can check the progress by clicking the yellow lightning icon at the lower-right hand side.

[satscraper]

Hi, I'm new to the Lightning Network and I'd like to try it firstly with my favourite wallet, electrum, even if I haven't heard the best about its LN functionalities. I believe that this is the thread to discuss my problems/queries about it.

I've opened Electrum Testnet and I've enabled LN. I want to open a channel to transact some funds with my other wallet.

Hi, probably I’m at the same stage as you were a year ago but can not move further to open LN channel in Electrum connected to testnet as the wallet's Open Channel button remains in the gray state. The wallet is topped up with 0.01 tBTC which, from my understanding, is enough for channel support. The button stays inactive no matter whether trampoline is disabled  or not. I would appreciate any suggestion on how to overcome things that block me from  LN channel opening with Electrum.

[nc50lc]

-snip- but can not move further to open LN channel in Electrum connected to testnet as the wallet's Open Channel button remains in the gray state. The wallet is topped up with 0.01 tBTC which, from my understanding, is enough for channel support. The button remains inactive no matter whether trampoline is disabled  or not. I would appreciate any suggestion on how to overcome things that block me from  LN channel opening with Electrum.

The two things that you may have missed are:

• Lightning should be enabled in the menu "Wallet->Information" if it's not ticked at least once yet (if it's created by an older version).
• The wallet's script (address) type should be Native Segwit ('bc1' address), other types including 2fa aren't compatible with Lightning.

[satscraper]

-snip- but can not move further to open LN channel in Electrum connected to testnet as the wallet's Open Channel button remains in the gray state. The wallet is topped up with 0.01 tBTC which, from my understanding, is enough for channel support. The button remains inactive no matter whether trampoline is disabled  or not. I would appreciate any suggestion on how to overcome things that block me from  LN channel opening with Electrum.

The two things that you may have missed are:

• Lightning should be enabled in the menu "Wallet->Information" if it's not ticked at least once yet (if it's created by an older version).

Thanks, that helped. Now  I have the choice between two options one of which is Remote Node ID and this is exactly  what I would like to use. But I'd like to have channel exclusively between two wallets I own, no middle-position node in between. Is that possible or the only way for me  to have my wallets LN-connected  is to establish connection of each of two wallets to one and the same  known peer?

Edit. Sorry, got it how can I do what I want. All I need is  to look again into Wallet->Information to get ID for my second node  

[nc50lc]

-snip-
Thanks, that helped. Now  I have the choice between two options one of which is Remote Node ID and this is exactly  what I would like to use. But I'd like to have channel exclusively between two wallets I own, no middle-position node in between. Is that possible or the only way for me  to have my wallets LN-connected  is to establish connection of each of two wallets to one and the same  known peer?

Those two are the only option if "Trampoline Routing" is enabled.
You can customize the remote node once you've disabled the said feature in the settings.

However, I haven't succeeded yet with creating a channel between two Electrum wallets.
You can try though - by providing each other's 'Lightning Node ID' as the "Remote Node ID" (Wallet->Information) followed by the IP address and port.
eg: 02d50fdf1806b54aee46a0ed8c6d8512bee87e88e25029f3384a983c43c5d6a16c@111.111.111.111:9735
But like I've said, it never worked at my end.