📅 Original date posted:2023-03-02
🗒️ Summary of this message: Improvements to Lightning Network routing include all nodes on the route receiving the same amount to reserve, simplifying rendezvous routing, and eliminating the need for an HTLC onion in the second step.
📝 Original message:
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
g0b1el [ARCHIVE] /
npub1rs…6p2yt
2023-06-09 13:12:52
in reply to nevent1q…s3vr
Author Public Key
npub1rszl6nxsjfym4f7cuml6gsm54z50na85d6xxdrljedq0al77j5psj6p2ytPublished at
2023-06-09 13:12:52Event JSON
{
"id": "7e8a91ebb77ccd98523ac49e6b865ea33b9524068d481d033374f375f741123f",
"pubkey": "1c05fd4cd09249baa7d8e6ffa44374a8a8f9f4f46e8c668ff2cb40feffde9503",
"created_at": 1686316372,
"kind": 1,
"tags": [
[
"e",
"6cf2bac30f5e1789fe9b3a7f4860def4a1b1e5359b17d12510670f19866a24a6",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2023-03-02\n🗒️ Summary of this message: Improvements to Lightning Network routing include all nodes on the route receiving the same amount to reserve, simplifying rendezvous routing, and eliminating the need for an HTLC onion in the second step.\n📝 Original message:\nThere are two more improvements I missed in my first mail.\n\nThe 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).\n\nAnd 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.\n\nBest Regards,\ng0b1el\n\n\u003e 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",
"sig": "d3f10dae8536a653d5094d2048c85bd2888bf4c783f287501329585d150601c5ad5c2f3e90c3ad4ce0c59608bc90cfd7f605d8f8d7088ab008874e4689f40d6f"
}