Arguably a low-priority bug since no current node ever generates routehints longer than one hop. However, it is possible as an edge case, if the destination is directly accessible *and* supports multiple channels, that we route through the destination, one of the *other* channels it has not in the routehint, to the entry point, and then through the routehint. This change removes the risk of the above edge case. Changelog-None: arguably a low-priority bug.
12 KiB
12 KiB