Open macanudo527 opened 2 years ago
Completely agree. I think the information should end up in one of the following (perhaps both):
It may be enough to add an optional Notes field to HistoricalBar, populated with this information. Then the transaction resolver can append the HistoricalBar notes to the transaction ones.
The Notes field is good I think. Users can then optionally pull a more detailed, longer report with this included if anybody needs it, otherwise they can just use the standard report.
Once the CCXT plugin is up and running it would be useful to be able to have some kind of paper trail exist on how the price routing occurred.
For instance, how the CCXT converter plugin found the fiat value of BETH, so that it can be available for the report that is generated in RP2. This would entail listing the market, exchange, and candle where the price was retrieved for each 'hop'. Something like the following:
This would be useful if a detailed audit did occur and the user would have to explain how they came about the pricing. This hop data would need to be stored in what is returned from
get_historic_bar_from_native_source()
(I think). Maybe add it toHistoricalBar
or an extended class for 'routed' pricing?