Topic: The Lightning Network FAQ - page 20. (Read 33287 times)

Here's my current understanding of how the system works:

0) Lightning nodes constantly use the gossip protocol (bolt07) to forward/receive "node_announcement", "channel_announcement", "channel_update" messages and maintain a local view of the whole network.
1) Alice receives a payment invoice from Eric which includes information like: Eric node's public key, payment hash, amount, expiry (date) and cltv expiry.
2) Alice constructs a path to Eric using her local map of the network. She tries to find the cheapest and the shortest route. The longer the route, the higher the risk that funds will get stuck during routing.
2a) She prepares "onion_routing_packet" which includes encrypted routing information for each hop.
3) Alice sends "update_add_htlc" message to Bob, which includes the "onion_routing_packet" (which is the same for all peers), the amount, the payment hash and cltv expiry.
4) Alice and Bob sign a new commitment transaction with an HTLC output.
5) Bob sends "update_add_htlc" to Carol with the same "onion_routing_packet".
6) Carol and Diana, Diana and Eric do the same.
7) Eric sends "update_fullfil_htlc" message to Diana, which includes the payment secret.
8) Eric and Diana remove the HTLC output and update balances by signing a new commitment transaction.
9) Diana sends "update_fullfil_htlc" to Carol with the same payment secret and they update the commitment transaction.
10) Carol and Bob, Bob and Alice do the same.

Comments:

3) The amount Alice sends is actually bigger than the one in the invoice as she must account for the fees. Each hop forwards the HTLC with a smaller amount and keeps the difference. If some hop tries to claim higher fees than Alice expected, the next node in the route will fail the payment as the routing instructions say how much one's node is supposed to forward.

If Bob doesn't have enough coins to forward the payment on his side of the channel with Carol, he must send "update_fail_htlc" message and Alice needs to try sending the payment through another route.

All channels use the same payment hash. It is safe because HTLC outputs require both the payment secret and HTLC signatures, which can be produced only by channel partners, to be spent. See this post for explanation.

Do you already have a channel from your C-Lightning node to your Electrum node?
Because a reason for the C-Lightning node to reject a channel opening could be that it is configured not to allow more than a single channel between two peers.

Other than that, it's possible as mentioned by darkv0rt3x that sometimes the gossip network doesn't propagate the IP of nodes completely so in addition to the node ID you need to specify the IP as well. However, if this was the issue, I'd expect an error message more akin to 'Could not find node' or something of this sort, and not a connection reject.

Side question: why are you trying to use Electrum for Lightning all the time? Why not whip up a second C-Lightning or lnd node?

Is there anyone who understands what's wrong with my node?
[~]

Since command mentioned by @Rath_ use single quote as boundary of the array, you don't need to add backslash before double quote inside the array.

Is there anyone who understands what's wrong with my node? While I can create channels with other nodes I can't create a channel from Electrum as it can't establish a connection: https://1ml.com/testnet/node/039a7e0982d3b0f967dfc18b8b69c9e8cafd035985eff1832258daf08de119b10e

I keep getting this when I enter my node_id@onion_url:


And it's weird, because it doesn't return the problem. It just says there is one, which makes me believe the developers aren't aware it exists.

302030 2022-01-17T21:10:20.272Z DEBUG   connectd: Now try LN connect out for host ln1qwd8uzvz6wc0je7lcx9ck6wfar906q6eshhlrqeztrd0pr0prxcsuagtc2y.lseed.darosior.ninja
302031 2022-01-17T21:10:20.273Z DEBUG   039a7e0982d3b0f967dfc18b8b69c9e8cafd035985eff1832258daf08de119b10e-connectd: Connected out, starting crypto
302032 2022-01-17T21:10:20.540Z DEBUG   039a7e0982d3b0f967dfc18b8b69c9e8cafd035985eff1832258daf08de119b10e-connectd: Failed connected out: Error connecting to ln1qwd8uzvz6wc0je7lcx9ck6wfar906q6eshhlrqeztrd0pr0prxcsuagtc2y.lseed.bitcoinsta       ts.com: Tor server reply: host unreachable. ln1qwd8uzvz6wc0je7lcx9ck6wfar906q6eshhlrqeztrd0pr0prxcsuagtc2y.lseed.bitcoinstats.com:9735: Connection establishment: Connection refused. ln1qwd8uzvz6wc0je7lcx9ck6wfar906q6eshhlrqeztrd0pr       0prxcsuagtc2y.lseed.darosior.ninja:9735: Cryptographic handshake: peer closed connection (wrong key?).

I never tried this one before, but if even like that, it doesn't work, you may have to escape the double quotes with a backslash. I usually run into problems when I use these commands that requires arrays of json objects.
For instance, to create a raw transaction I actually have to use:

As you see, there are some double quotes that needs to be escaped (the ones inside the json array object), otherwise, bash will "consume" a layer of them and then, the json object is "sent" to the RPC command wrongly constructed!

This should work for you:


Make sure to change minchannels if you add more destinations.

bitcoin-cli createrawtransaction "[{\"txid\":\"tx_hash_here\", \"vout\":1}]" "[{\"bitcoin_adress_here\":0.05},{\"bitcoin_change_adress_here\":0.049}]" 0 true

How do you insert an array, or in this situation the destination, properly? There are lots of ways I can think of...

lightning-cli multifundchannel -k destinations='[{"id": "node1" ,"amount": amount1},{"id": "node2" , "amount": amount2}]' feerate=1000perkb minchannels=2

For example, I have read about instances in which an LN node failed, the user restored from a backup that did not have the correct channel state, which resulted in the backup-restored node trying to close the channel via an old channel state.

What's the best channel_capacity/network_contribution ratio? For instance, would it be more contributive to open 100 of 0.01 BTC rather than 2 of 0.50 BTC?

Also, how do I choose the proper nodes to do this?

Also, how do I choose the proper nodes to do this? I had read about triangles, but I'm not sure if that's what I'm talking about.

Yesterday, I performed a triangle swap with two other bitcointalk members. Each of us opened a 0.05 BTC channel to the other person. This way, we gained additional 0.10 BTC capacity, which means that this swap has doubled my node's capacity. I paid 222 sat for the opening transaction. We dropped the fees to 0 and TheJuice's script took care of the rebalancing. On the same day, I routed 6 transactions from the channel I opened and I got paid 222.76 satoshi. The channel paid itself off in just a few hours.

If you ever wondered how often someone is penalized for fraudulent behaviour, forkmonitor keeps track of all penalty transactions ever broadcast. Apparently, there have been 419 unsuccessful cheat attempts with a total of ~5.13 BTC at stake since the end of 2017.

Just like scammers and governments support the Tor network by running their own compromised nodes As long as enough scammers and competing governments join, and as long as users are aware of the risks, none of this stops the network.

I successfully opened a channel with Boltz to make it work. It appears that the lightning daemon just needed a restart. Okay, so I sent them 0.0025 LN-tBTC and have probably increased my receiving capacity. Shouldn't I now be able to send my node a few sats? Why do I still get the same error?

Is there any other client you advice me to use instead of Electrum? No matter how much I've googled I haven't understood why this happens...

Well, it's as the messages say. You have no route to Boltz.

For a quick hack, you can kind of 'force detach' it by adding a & at the end like this: ./lightningd &

Can someone solve me these queries that I have? So, I've gone to testnet.boltz.exchange to increase my receiving capacity as a lightning node. You just give LN-BTC and receive BTC, hence you've increased your receiving capacity by spending some your channel's reserve.

Alright, so I've tried this with my Electrum. I opened up a channel with somebody, sent the LN-BTC got my BTC, everything went fine. But, what exactly happens when I try the same with my lightning node?

Secondly, why does my lightningd log show these?

Thirdly, why does the lightning daemon closes when I close the Windows' cmd? Normally, when I'm ssh-ing using the cmd and close it, nothing changes from the RPi.

Just like scammers and governments support the Tor network by running their own compromised nodes As long as enough scammers and competing governments join, and as long as users are aware of the risks, none of this stops the network.

Since at least 2017, a mysterious threat actor has run thousands of malicious servers in entry, middle, and exit positions of the Tor network in what a security researcher has described as an attempt to deanonymize Tor users. The Record reports:
Tracked as KAX17, the threat actor ran at its peak more than 900 malicious servers part of the Tor network, which typically tends to hover around a daily total of up to 9,000-10,000.
...

Plus Chain Anals’ tracking of Lightning transactions actually helps increase the liquidity in the network and helps it scale, and makes it function better.