Describe the solution you'd like
Right now pathFinder grabs orderbooks for its calculations separately for each payment path, and this leads to duplicate API calls; if XLM-BTC is in more than one path, pathFinder queries Horizon that pair for each path that contains it.
Requirements
Have pathFinder generate a standalone list of the trading pairs it needs when initialized, idependant of the individual path records
Query each pair once for each cycle and use the query response for all paths that need it
Describe the solution you'd like Right now pathFinder grabs orderbooks for its calculations separately for each payment path, and this leads to duplicate API calls; if XLM-BTC is in more than one path, pathFinder queries Horizon that pair for each path that contains it.
Requirements