Good morning again Rene,
An observation I would like to make is that, as I understand it, the model
inherently assumes that all nodes are equally likely to be payer and equally
likely to be payee.
While in a complete economy this is to be expected (the "customer" of a
"merchant" will be an "em
Good morning Rene,
I am glad my question has triggered such interest from you!
I will confess that I do not yet understand the math you demonstrated and have
not seen your program at all yet.
It is a good thing as well that it can be used to derive routehints for
invoices.
I do have a follow-u
Good morning ZmnSCPxj, and list,
the answer to your question is absolutely yes and we can can achieve this
actually in a very simple and elegant way.
Please find attached a clear and simple adaption of the algorithm described
from the paper for a general multipath payment and a small python code
Good morning Rene, and list,
It seems to me that the rule used here might be useful to guide how to split a
payment for multipath as well.
For example, consider the case where a payer Alice has channels to Bob and
Charlie.
* Alice-Bob has A=0.5, B=0.5
* Alice-Charlie has A=0.5, C=0.5
In that
Good morning Rene,
What no JIT-routing?
> # Roadmap for BOLT 14 (Fee free Rebalancing Transport):
>
> If no strong objections exist I would try to extend the BOLTs with the
> following to be able to implement the rebalancing algorithm across the
> network (as with JIT routing nodes can already
Dear fellow Lightning Developers,
today my research paper (together with Mariusz Nowostawski) "*Imbalance
measure and proactive channel rebalancing algorithm for the Lightning
Network*" was published on arxiv: https://arxiv.org/abs/1912.09555 The
LaTeX project as well as the code for the experimen
