Recently coingecko requests started returning an error due to not having a user-agent, which is easy enough to resolve, however we must consider the possibility that compatibility could break during production at some point.
One way we could deal with this is inserting a proxy API that handles the coingecko requests, so we can update this API in the case of future compatibility issues. This proxy could also cache results to prevent rate limiting, and our nodes could request via the proxy instead.
Recently coingecko requests started returning an error due to not having a user-agent, which is easy enough to resolve, however we must consider the possibility that compatibility could break during production at some point.
One way we could deal with this is inserting a proxy API that handles the coingecko requests, so we can update this API in the case of future compatibility issues. This proxy could also cache results to prevent rate limiting, and our nodes could request via the proxy instead.