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

Hotfix/staking kpi reachability #358

Merged
merged 103 commits into from
Dec 16, 2024
Merged

Conversation

keshav1998
Copy link
Collaborator

No description provided.

Bets class objects will now also tracking the amount being invested.
invested amount during update should be added instead of updating the new value
the new variable name signifies that it is an internal calculated value
The sampling logic follows the specified priority logic:
        1. Filter out all the bets that have a processed_timestamp != 0 to get a list of new bets.
        2. If the list of new bets is not empty:
           2.1 Order the list in decreasing order of liquidity (highest liquidity first).
           2.2 For bets with the same liquidity, order them in decreasing order of market closing time (openingTimestamp).
        3. If the list of new bets is empty:
           3.1 Order the bets in decreasing order of invested_amount.
           3.2 For bets with the same invested_amount, order them in increasing order of processed_timestamp (least recently processed first).
           3.3 For bets with the same invested_amount and processed_timestamp, order them in decreasing order of liquidity.
           3.4 For bets with the same invested_amount, processed_timestamp, and liquidity, order them in decreasing order of market closing time (openingTimestamp).
Updates the investment amount and transaction timestamp if reedeem round is reached from post_tx_round
@keshav1998 keshav1998 added the enhancement New feature or request label Nov 22, 2024
annasambrook
annasambrook previously approved these changes Nov 22, 2024
Co-authored-by: Anna Sambrook <[email protected]>
Adamantios

This comment was marked as resolved.

Adamantios
Adamantios previously approved these changes Dec 6, 2024
@Adamantios Adamantios changed the base branch from main to develop December 9, 2024 09:37
@Adamantios Adamantios dismissed their stale review December 9, 2024 09:37

The base branch was changed.

Adamantios
Adamantios previously approved these changes Dec 9, 2024
annasambrook

This comment was marked as resolved.

Otherwise, the `tx_submitter` will not be available in the db for the current period, and either way it would not make sense to update the transaction information for a past period's decision.
@Adamantios Adamantios dismissed stale reviews from annasambrook and themself via e0a0fad December 9, 2024 14:20
annasambrook
annasambrook previously approved these changes Dec 9, 2024
Adamantios
Adamantios previously approved these changes Dec 9, 2024
Previously, we were only aware of a new epoch if our own agent was the one to call the checkpoint. If any other agent had called it, then we would never be aware of this event.

Instead, we are now tracking changes to the ts checkpoint of the contract which only and always gets updated after a new epoch is triggered.
@Adamantios Adamantios dismissed stale reviews from annasambrook and themself via de664a8 December 11, 2024 15:50
@Adamantios Adamantios force-pushed the hotfix/staking-kpi-reachability branch from de664a8 to 48d1f1e Compare December 11, 2024 16:07
@Adamantios Adamantios force-pushed the hotfix/staking-kpi-reachability branch from 48d1f1e to b8190fc Compare December 11, 2024 16:29
@Adamantios Adamantios merged commit ff68801 into develop Dec 16, 2024
18 checks passed
@Adamantios Adamantios deleted the hotfix/staking-kpi-reachability branch December 16, 2024 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants