Rusty Russell on Nostr: Today, I got back to working on "askrene" for Core Lighting. The idea is to extract ...
Today, I got back to working on "askrene" for Core Lighting. The idea is to extract the core logic of the experimental "renepay" plug-in into an Oracle you can ask for routes (and provide feedback on what happened). This is much more composable: anyone can write a plugin which uses this information, *or* an alternate pathfinding plugin to replace it.
It's built around the idea of "layers" which are where information lives: you tell it what layers to use when you ask for a set of routes. This has many uses: you might have route hints or blinded paths you want (or have to!) use. You might want to constrain a payment to a particular channel for rebalancing, etc.
In theory, these layers can be exported and imported: you can share information about the state of the network between nodes. I'm sure there's a pile of obfuscation needed to preserve privacy in this case, but it's an interesting idea...
Published at
2024-05-22 07:20:41Event JSON
{
"id": "29c6965f8de3f29611248ba3e01eec16e36a74e55af4b0bd3ee0f35e54351c50",
"pubkey": "f1725586a402c06aec818d1478a45aaa0dc16c7a9c4869d97c350336d16f8e43",
"created_at": 1716362441,
"kind": 1,
"tags": [],
"content": "Today, I got back to working on \"askrene\" for Core Lighting. The idea is to extract the core logic of the experimental \"renepay\" plug-in into an Oracle you can ask for routes (and provide feedback on what happened). This is much more composable: anyone can write a plugin which uses this information, *or* an alternate pathfinding plugin to replace it. \n\nIt's built around the idea of \"layers\" which are where information lives: you tell it what layers to use when you ask for a set of routes. This has many uses: you might have route hints or blinded paths you want (or have to!) use. You might want to constrain a payment to a particular channel for rebalancing, etc.\n\nIn theory, these layers can be exported and imported: you can share information about the state of the network between nodes. I'm sure there's a pile of obfuscation needed to preserve privacy in this case, but it's an interesting idea...",
"sig": "1e0b09121134b18d4e3de6a4223dcf0b1e9e032b6e1c6c146616689dbd5e210de7e5a5c38b6cd8965b0e3fbecf5398e0d28d39fa2fb3637508c650e58badc85e"
}