-
Notifications
You must be signed in to change notification settings - Fork 22
Game details API is showing non-games #10958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Pretty convinced this is just the fact that all but 3 of our rewards on mainnet predate the games code going to mainnet. Hence they dont have game IDs and everything falls apart. If we see things work tonight for the Eigenpoints market I think we close this. We may consider cancelilng and restarting the othe reward transfers so they get a game ID in case that breaks something unexpected |
As mentioned on the slack threads, the game API docs are either wrong, or at best confusing. When specifying from/to epoch parameters, the range of data returned by the API is in fact capped to 30 epochs regarldess of the request parameters specified. It'd be best to update the docs, perhaps including some examples for clarification: Let's say the current epoch is 1000
|
Happy we can close this |
Desc
On mainnet there is a transfer defined thus:
So you can see it is LP rewards and is not a game.... not really.
But if you query the game details API you see results for it ... many times ... which obviously is basically just showing the LPs getting rewards.
This seems odd ... not sure it will impact too much at the moment ... because we only navigate to the game results from the team or the game therefore you wont see it ... but it seems odd.
Maybe we currently define ALL rewards with a dispatch strategy as a "game"?
The text was updated successfully, but these errors were encountered: