Good morning Robert,
> Good Morning ZmnSCPxj!
>
> I was thinking using the normal onion-routing, probably modified in some way
> so it can read and modify max. Must admit I haven't studied that part at that
> level at all.
>
> For simple three-member constructs it could be enough with a simple n
Good Morning ZmnSCPxj!
I was thinking using the normal onion-routing, probably modified in some
way so it can read and modify max. Must admit I haven't studied that part
at that level at all.
For simple three-member constructs it could be enough with a simple
non-onion message that A asks B if it
Good morning Robert,
I assume, this functionality is transported also via the same
onion-routing-packet style that current payment routing uses?
If so, then it seems this feature can be used by a payer and payee to
coordinate to locate some route that would, if paid normally, charge fees, but
Dear All,
I'd like to suggest a new function in the network, "Free Rebalancing
Proposals"
It is a fee-less, omni-beneficial rebalancing scheme
Background:
I currently balance my nodes in the following way, extremely simplified:
1) Identify channels that have too low remote_balance (A) and too l
