You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This order of operations means that we may run out of paths in blindedpath.BuildBlindedPaymentPaths and we wont go back and try some of the paths that we initially found by ChannelRouter's findBlindedPaths.
What we instead want is for blindedpath.BuildBlindedPaymentPaths to be able to continue with the iteration through possibly all of the routes found in findBlindedPaths until it reaches the max specified by MaxNumPaths.
The text was updated successfully, but these errors were encountered:
Today, if we are constructing set of blinded payment paths to add to an invoice, we:
MaxNumPaths
routes to our own node that are considered blinded path candidates.blindedpath.BuildBlindedPaymentPaths
which attempts to use each path to build a valid blinded pathblindedpath.BuildBlindedPaymentPaths
finds that it cannot use one of the paths it was given, it skips it and moves on to the next oneThis order of operations means that we may run out of paths in
blindedpath.BuildBlindedPaymentPaths
and we wont go back and try some of the paths that we initially found byChannelRouter
'sfindBlindedPaths
.What we instead want is for
blindedpath.BuildBlindedPaymentPaths
to be able to continue with the iteration through possibly all of the routes found infindBlindedPaths
until it reaches the max specified byMaxNumPaths
.The text was updated successfully, but these errors were encountered: