The State is definitely not ourselves and it's neither there for our own interests. We are more likely their subjects, taxlaves at their mercy.

Still work in progress but public at

GitHub

GitHub - Lagrang3/mcf-algorithms

Contribute to Lagrang3/mcf-algorithms development by creating an account on GitHub.

and soon to be included in Core-lightning's renepay command.

Tired of getting payment timeouts trying to pay with my own core-lightning node (and having to fallback to Phoenix) while exploring Lugano. I have decided to set renepay as the default payment command. Get the plugin at github.com/lagrang3/default-renepay So far this has solved my routing issues. Let me know if it works for you too.

#amethyst, #nostr, #featurerequest, @Vitor Pamplona. Auto translation is great, but I can only set one language in the Amethyst app. However I can speak 3 languages, and I am currently learning others, thus I would like that notes if detected to be written in one of my favorite languages to show as it is, and only auto translate otherwise.

I have been fixing renepay lately and thanks to some insightful discussions and brainstorming with René Pickhardt we have had great improvements. In summary, the current Mininum Cost Flow algorithm (MCF) cannot allocate fees as part of the payment amount due to the sats conservation assumption that the only source and sink of flow are the sender and recipient nodes. Once fees are added on top this resulted in channels being asked to forward more sats than their probable available liquidity and consequently possibly an infinite loop of failures. To fix this we take the routes computed by the MCF and reduce their sending amount to fit all liquidity constraints: fee, uncertainty and max_htlc; then deficit in the delivering amount is redistributed among the other routes or reallocated in a new MCF computation if necessary. More details at this PR:

GitHub

renepay: accomodate fees in the payment flow by Lagrang3 · Pull Request #6893 · ElementsProject/lightning

Min. Cost Flow (MCF) does not resolve the correct amount in channel forwarding because the algorithm dismisses the amounts paid as fees to the rout...

before: after:

how much did you pay today in LN fees?