Bolt11 route hints are imported to the graph used for pathfinding throughout the payment's lifecycle, as seen lnd/routing/payment_session.go

This means, that we should be able to acquire multiple quotes from our peers, and encode multiple RFQ scids in the invoice, giving more routing options to the sender

It seems we have another motivation for this in that we can get a competitive bid from the peers as well and choose the peers with best rates to include in the route hints.

We also need to consider multi path payments. Do we want to request a quote for the full invoice amount with each peer or do we want to intentionally request a lesser amount with each peer so that the sender MUST use multi part payments and split the payment across several peers?

Another thing to consider is when defining the SATS amount in the invoice that is given to the sender, we need to use the worst quote of all the peers. In this case, if the sender happens to pay through the peer with the best quote, we will get some bonus assets.

We also need to consider multi path payments. Do we want to request a quote for the full invoice amount with each peer or do we want to intentionally request a lesser amount with each peer so that the sender MUST use multi part payments and split the payment across several peers?

Yeah that's a good point, I think we definitely need to over-quote, otherwise the sender would never be able to guess the exact amounts for each hop.

Another thing to consider is when defining the SATS amount in the invoice that is given to the sender, we need to use the worst quote of all the peers. In this case, if the sender happens to pay through the peer with the best quote, we will get some bonus assets.

Also great point, we'd have to have some smart logic involved here, perhaps pick the worse rate only if there's a small spread over the quotes. If a peer provides me with a quote that deviates by more than a certain percentage/threshold, I'd rather kick him out of the "quote set" than include him.

Also great point, we'd have to have some smart logic involved here, perhaps pick the worse rate only if there's a small spread over the quotes.

I think we always have to pick the worst quote regardless of the spread, but I agree that

If a peer provides me with a quote that deviates by more than a certain percentage/threshold, I'd rather kick him out of the "quote set" than include him.

but say we have one quote that is way better than all the others, we probably don't want to throw that one out just because it deviates a lot (unless we think that node is going to have low reliability of forwarding payments). It seems like we would want to keep it and if we are lucky and get a better deal then we'll take it. But we do want to throw out quotes that are much worse than all the others.