I also have mixed feelings. While I love c-lightning's dual-funding and multifund, I also feel like I am missing out on something. On the other hand, I have seen complaints on Reddit that LND can't keep up anymore if you are running a medium sized node on a low-power device like Raspberry Pi, which many people do because of various out-of-the-box LND based nodes. Anyway, I believe that it's important to support implementation diversification.

Would you mind sharing your node's id?

I couldn't find any other watchtower software for c-lightning as well. I still haven't set it up, but I can give it a try if you have any particular questions about it.

Co powiesz na serwer Electrum (ElectrumX, electrs) i do tego jakiś block explorer (mempool, esplora)? Obecnie korzystam z ElectrumX, którego baza danych zajmuje dodatkowe 73,5 GB na dysku, oraz z mempool, który łączy się bezpośrednio z moim serwerem Electrum.

I have been getting a lot of "Local_failed" routing attempts in RTL since the triangle swap. lightning-cli listforwards returns WIRE_TEMPORARY_CHANNEL_FAILURE for all of these recent transactions so I decided to investigate further. I turned on debug logging and here's what I found:


This way, you can learn which channel failed to route the payment and how large it was. RTL shows only the "IN" channel.


Thanks! I won't be able to come close to your node's capacity, but I will do whatever I can to help the network.

It's worth noting that you can make others wait longer to claim the funds than yourself. Currently, my node makes other people wait 432 blocks (~3 days), but I still accept channels with up to 2016 blocks (~2 weeks) delay. I don't mind waiting that long. Most people don't change the default value of 144 blocks anyway.

If you want to reject channels with excessive timelocks change either bitcoin.maxlocaldelay (LND) or max-blocktime-watch (c-lightning). If you want to force the other party to wait longer if they broadcast their commitment transaction change bitcoin.defaultremotedelay or watchtime-blocks (c-lightning). Note that those parameters do not affect existing channels.

Even if you overpay a Lightning invoice, which should never happen under normal circumstances since invoices encode the amount, the receiving node should accept up to twice the expected amount.


When a payment is being routed, intermediary nodes do not know the final destination and the final amount anyway. The routing path is constructed by the payer. If the payee doesn't like the final amount, they can simply fail the payment.

To put it in other words, intermediary nodes calculate the amount they need to forward based on the information provided by the sender, and not included in the invoice, which they never see anyway.

I have actually tried it out some time ago and I really liked that it supports keysend payments. Thanks for reminding me about it; I will add it to the list.

By the way, in case some of you missed it, I created The Lightning Network node experience thread in which I and a few other members shared our statistics and feelings about running a Lightning Network node.

If you just want to test out the Lightning Network then try using a custodial wallet like BlueWallet. You won't have to worry about opening your own channels and it should be easy to use. Once someone pays your invoice, you can use this website to choose a service which accepts Lightning payments.

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.

Note that on some days (ex. today) I routed a few small payments (< 1 sat). It's impossible to tell it from the graph at this point.

It is not completely impossible. Any payment can be split into many small chunks which can be routed through different routes. Still, it's not feasible for hundreds/thousands of dollars unless you are connected to a few large nodes. Also, employees might have to worry about inbound capacity, but I guess they will receive their salaries to a custodial wallet managed by OpenNode.

Thanks! That was much faster than I expected. I have just opened channel to TheJuice.

c674fb603e580cfebc44531ac2bb366697c5c92acf11139e77dd966272403255

Do both of you want to balance our channels through a circular payment after dropping the fees to 0?

TheJuice and I are looking for one more person to participate in a Lightning triangle swap. Feel free to join if you are willing to contribute 0.05 BTC!

https://lightningnetwork.plus/swaps/4879 pin:411f57359f

It basically proves that you are the owner of that particular address. Otherwise, they would not be able to tell if you are not just a random person who wants to take your donation away.

I am actually thinking about opening a channel to your node. Is there any particular reason why you reject channels smaller than 5 million satoshi? Do you want to avoid frequent rebalancing this way?

I see that quite few of you are running your own Lightning Network nodes. It would be great if you could share your experience and some data about routed payments in this thread.

Also, I am running a fairly small node. If anyone running c-lightning is interested in opening a dual-funded channel, I can guide you through the process. I have already opened 3 dual-funded channels with other bitcointalk members.

You need to use lightning-cli listforwards command to see the exact error. Here you can find a list of errors with explanations.


Maybe the payment was split into multiple chunks and some of them failed? It would make sense to route one part through you again if it worked in some previous attempt.

Yes.


Correct. If you attach your passphrase to a PIN, you will be able to switch between both wallets easily.


Yes.


I would use the Recovery Check app instead.

Probably no one except some Ledger employees. You can contact their support but you will very likely get a reply like "when it's ready". Why would you need to know that anyway?

Thanks @darkv0rt3x for sharing your data. As I have already told you, I spent some time manually adjusting the fees for each channel every few days and it looks like I found the right values.

November looks really promising for my node. I am also about to open two new channels beside the one with n0nce.

Masz już jakieś konkretne plany na czym go postawisz? Raspberry Pi? Stary laptop? A może jeszcze coś innego?


Zachęcam do podzielenia się nimi w tym konkretnym wątku, żeby osoby zainteresowane tym tematem przypadkiem go nie przeoczyły. Nie bez powodu wątek FAQ ma ponad 50 stron