There are two more improvements I missed in my first mail.
The first one is that all the nodes on the route get the same amount to
reserve. So there is no need to put the amount inside the onion. This way node
can fail reservation faster if there is no reservation balance left without
opening the onion. Also, the onion gets smaller, and now it holds just the next
hop information. This might simplify rendezvous routing(needs to explore this
further).
And the second improvement is that we don't need HTLC onion in the second step.
Route hops already contain all the information to create HTLC. So all that's
left to do is for the sender to sign the commitment and to revoke the state
with a first node in the route. Thus increase in payment latency would be just
one more call between the route nodes.
Best Regards,
g0b1el
> If ASCII graphics are not rendering correctly, you can read the proposal on
> the mailing list archive, where for some reason are rendered correctly -
> https://lists.linuxfoundation.org/pipermail/lightning-dev/2023-February/003867.html
___
Lightning-dev mailing list
Lightning-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
