Description
In this RB PR, we started querying MC to choose the best paths towards us but realistically, MC wont have much (if any) data about links in this direction (all of its data currently comes from sending out).
If we use a blinded path to receive, however, we will start gaining some info about success pairs in the correct directions. So this PR will cover tracking this & updating MC accordingly.
How?
-
First, we will want to adjust the data required by mission control to create a mission control entry. This is covered by: routing+channeldb: use a more minimal encoding for MC routes #8911
-
Then, we need to start persisting some more info with invoices so that we can add success pairs to MC for which ever blinded path the payment came through on. We know which blinded path it is coming through on cause we can see the incoming blinded key which will be unique to the path. So either we need to: A) store a map from incoming blinding key -> mc route data OR B) just store map from incoming blinding key -> associated session key for the blinded path & use that to then decode the blinded path blobs in the invoice. I'll need to investigate further to see which option is better.