You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the production environment has both a rinkeby and a mainnet chainlink node, but the api is configured to only support either prod (mainnet) or development (rinkeby) configs. we need to be able to discern between requests comingh from either of the nodes and route data accordingly. specifically, a chainlink request includes a callback response url and that response url has the name of the service in it (chainlink-rinkeby or chainlink-mainnet). depending which of those re receive, the request should route correctly. anywhere there is a check for if "API_MODE == prod" or that sort of thing we need to consider if the ocntrol flow needs to be modified to take the request origin into account
The text was updated successfully, but these errors were encountered:
the production environment has both a rinkeby and a mainnet chainlink node, but the api is configured to only support either prod (mainnet) or development (rinkeby) configs. we need to be able to discern between requests comingh from either of the nodes and route data accordingly. specifically, a chainlink request includes a callback response url and that response url has the name of the service in it (chainlink-rinkeby or chainlink-mainnet). depending which of those re receive, the request should route correctly. anywhere there is a check for if "API_MODE == prod" or that sort of thing we need to consider if the ocntrol flow needs to be modified to take the request origin into account
The text was updated successfully, but these errors were encountered: