Rusty Russell [ARCHIVE] on Nostr: 📅 Original date posted:2018-10-09 📝 Original message: Pierre <pm+lists at ...
📅 Original date posted:2018-10-09
📝 Original message:
Pierre <pm+lists at 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.
📝 Original message:
Pierre <pm+lists at 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.