Author: ZmnSCPxj 2018-11-09 12:02:21
Published on: 2018-11-09T12:02:21+00:00
During a discussion with representatives from Nayuta, the topic of a "trustless" pathfinding service was brought up. A scenario was presented where a paying Lightning node cannot keep a complete routemap and desires a service that can contain it without knowing the payer and payee. Initially, a solution was proposed where the paying node provides several nodes in an ordered list, including itself and the destination, and the routing service creates a long route passing through all the nodes in the specified order. However, upon reconsideration, this solution was deemed unsatisfactory. The proposed solution previously mentioned had several constraints, such as the payer needing to precede the payee on the list, and the nodes needing to be within 10 nodes of each other. Additionally, the routing service maintains one or more Lightning nodes with higher than typical fees to bias pathfinding towards those nodes. Further exploration of the issue is needed to find a better solution for a trustless pathfinding service.
Updated on: 2023-05-25T15:50:49.626452+00:00