> But there's no reason to believe that the invoicer has more knowledge about
> all but the last hop.
I disagree: there is a good chance that the receiver is a 24/7 running
merchant/website, with a full up-to-date view of the network, whereas
the payer is most likely a mobile wallet with less
acc
Good morning Matt,
In my implementation that might get into c-lightning (i.e. my pull request,
which I should probably update some time before universe heat death) the r=
fields are preferred, but if unable to find routes to the nodes indicated in
the r= fields, we always fall back to our known
Matt Corallo writes:
> On a related note, it would be nice to get some clarity on appropriate
> usage of the r= field here.
> The way I had implemented it initially was that if an invoice had an r=
> field any publicly-discovered last-hop routes would be ignored as the r=
> data is most likely mor
