I agree the r-fields are useful to populate for public channels in many situations, but care must be taken to not _always_ try them first without accounting for potentially high fees on those channels.
- Johan On Wed, Oct 10, 2018 at 5:46 AM Rusty Russell <ru...@blockstream.com> wrote: > Pierre <pm+li...@acinq.fr> writes: > >> 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 > > accurate/partial/out of date information. > > > > At least this is what we are seeing on the current mainnet. Routing > > table sync is hard on mobile clients, and I think that it makes sense > > that receivers "help" senders, after all incentives are aligned. > > Good qualification; I agree. Certainly if the payer knows its > information is less reliable it should prefer the provided route. > > Cheers, > Rusty. > _______________________________________________ > Lightning-dev mailing list > Lightning-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev >
_______________________________________________ Lightning-dev mailing list Lightning-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
