Nostr Web Client

#CLN release 24.11.1, for those fans of xpay. I've been impressed how many people are testing it, and especially those who go all in on the #reckless "xpay-handle-pay" setting!

BTW: did you know you can use the "config" command to set `xpay-handle-pay` *on the fly*?

https://github.com/ElementsProject/lightning/releases/tag/v24.11.1

Eluc 1y ago

Why reckless? My fresh install of CLN never finding routes, even if I was one hop away with 10x the liquidity. I was told to use xpay and use xpay-handle-pay to make it works in Zeus and other connected app. But I have no idea what it's doing differently, why pay is not working proprely (pay in renepay, right?) and now I learn that there is a risk. What is the risk?

TBH I'm sometimes regretting I went to CLN for my new node, it seams super alpha and badly supported. LND was much more reliable and always supported day one by apps (LNbits, Zeus, Thunderhub, NWC...).

I just prefer the CLNrest with rune restrictions but it's super hard to setup beside the full access one, and in the end if you connect everything with Alby Hub/NWC you can set restriction as well, in a super easy GUI way.

Reply to this note

Please Login to reply.

Discussion

Rusty Russell 1y ago

I understand this! We are definitely less polished in many areas. Progress can be slower than I want.

This is software, so there's always a chance if bugs, and xpay is new.

The main risk is that *none* of your payments work, because I missed some case which applies for you. But we could also have bugs which pay too much in fees, for example.

Eluc 1y ago

Ok so the risk is quite limited for my usage.

I was probably a bit rude, sorry for that, most of the comfort I attributed to LND is due to better integration in third party app, it's not really CLN fault and I understand apps support the leading implementation first.

Anyway, once LNBits will fully support CLNrest (my c-lightning-rest plugin stopped working after a week for no apparent reason and I could never restore it) I might have everything I need anyway, with NWC as an extension.

Maybe an easier way to rebalance and force payment throught a certain channel would be welcome, I gave up on this filter layer thing, looks super complicated.

Rusty Russell 1y ago

I haven't tried lnbits, but glancing at the docs, I would usually use the CoreLightningWallet backend, but that is only if lnbits is on the same machine.

Biasing a channel you want to balance may give you some passive balancing, as other payments go out, but unless you do lots of payments I don't think it will be very effective. Most people use the rebalance plugin, but it's a bit primitive these days: we could write a better one...

Eluc 1y ago

Thanks for the answers. I tried the CoreLightning wallet connection, first it's connecting directly to lightning-rpc, so in case of a bugs/hack LNbits could drain all channels without limits. But c-lightning-rest is the same I guess, until it supports CLNrest with runes.

I still tried to use the lightning-rpc until I have a better solution but it never worked. I run each app by a separate user:group so lnbits cannot access lightning-rpc, even if it's part of the lightning group and the lightning-rpc has 777 permissions. Stuck there, nobody could help in the lnbits telegram as almost no one use it with CLN.

Rusty Russell 1y ago

It's very wise of you to run them as separate users, but you could have them all in the same group and make sure the directory for lightning RPC is accessible by that group as well as the file itself?