Skip to content
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

[Feature]: Publish ongoing game score snapshots during epochs #2239

Open
5 tasks
JonRay15 opened this issue Apr 3, 2024 · 1 comment · Fixed by #2242
Open
5 tasks

[Feature]: Publish ongoing game score snapshots during epochs #2239

JonRay15 opened this issue Apr 3, 2024 · 1 comment · Fixed by #2242

Comments

@JonRay15
Copy link
Contributor

JonRay15 commented Apr 3, 2024

Feature Overview

In order to make games more fun
We will work out how to publish snapshots of running game scores at intervals in the epoch
So that users can see how they are doing rather than just waiting until the very end to see what they have won

Proposal

Can we define some "calculation interval" or something on the game definition? We already have a "window length" which sets how many epochs the game is ultimately calculated over. We need some other parameter that allows us to get some interim snapshots of the data during the game. Maybe this calculation interval could be enforced to be 0 < x < 1 so that it is always some fraction of an epoch? Then we could work out what the min value of this is to avoid any kind of performance concerns?

Acceptance Criteria

  • I can get a view of my eligibilty across all metrics during the in-progress epoch
    • Open volume (whether we're meeting notionalTimeWeightedAveragePositionRequirement)
    • Traded volume (since soon we should be adding a tradedVolumeRequirement)
    • Total fees paid this epoch (since there is discussion on whether the reward cap could be used here too)
  • I can get a view of my my current place in the ranking for the reward metric

Feature test scenarios

Detailed scenarios that can be executed as feature tests to verify that the feature has been implemented as expected.

GIVEN (setup/context)
WHEN (action)
THEN (assertion) For example...
See here for more format information and examples.

Additional Details (optional)

Any additional information that provides context or gives information that will help us develop the feature.

@JonRay15
Copy link
Contributor Author

Happy to descope the traded volume part since we are not using that as an eligibilty check now as we have started using realised PnL instead (from another tickets)

@JonRay15 JonRay15 removed this from Core Kanban May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants