Got it, thanks for the explanation.
If the exchange rate data is not kept and “cached” on the canister, could this open up the exchange rate canister to a cycle drain attack?
According to some initial feedback from DFINITY it looks like HTTP calls are expensive (400M cycles per call). Since the exchange rate canister would be the one paying for the HTTP calls, how do you plan on keeping it topped up and preventing cycle drain overuse?