From johanth at gmail.com Wed Oct 10 11:57:11 2018 From: johanth at gmail.com (=?UTF-8?Q?Johan_Tor=C3=A5s_Halseth?=) Date: Wed, 10 Oct 2018 13:57:11 +0200 Subject: [Lightning-dev] RouteBoost: Adding 'r=' fields to BOLT 11 invoices to flag capacity In-Reply-To: <87pnwiljqz.fsf@rustcorp.com.au> References: <877ejg9avy.fsf@rustcorp.com.au> <504b31cc-fcb9-f433-32e9-00de9456461b@mattcorallo.com> <87r2h1m318.fsf@rustcorp.com.au> <87pnwiljqz.fsf@rustcorp.com.au> Message-ID: 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 wrote: > Pierre 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 at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: