-
Notifications
You must be signed in to change notification settings - Fork 23
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
Prorated rewards v2 #631
Open
cam-schultz
wants to merge
18
commits into
main
Choose a base branch
from
prorated-rewards-v2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+943
−172
Open
Prorated rewards v2 #631
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
4de2415
basic test passing
cam-schultz 2af7729
revert if no reward claimable
cam-schultz 1717d36
claimValidatorRewards remaining unit tests
cam-schultz 8220a73
correct uptime period calculation
cam-schultz 2025630
move uptime threshold check to PoSValidatorManager
cam-schultz 32f05d9
remove unused reward sparams
cam-schultz b61b8b2
add testing helpers
cam-schultz 776c72d
reorder methods
cam-schultz dd390a9
consistent messageIndex placement
cam-schultz 5a608bc
update abi
cam-schultz ec8b480
store uptime since validation start
cam-schultz c209726
Merge branch 'validator-manager' into prorated-rewards
cam-schultz 503da7d
format
cam-schultz d21de01
correct arg order
cam-schultz fac829a
calculate owed rewards by subtracting claimed rewards
cam-schultz ee8ac29
Merge branch 'main' into prorated-rewards
cam-schultz 27bf88f
Merge branch 'prorated-rewards' into prorated-rewards-v2
cam-schultz 5d82650
update bindings
cam-schultz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
257 changes: 231 additions & 26 deletions
257
abi-bindings/go/validator-manager/ERC20TokenStakingManager/ERC20TokenStakingManager.go
Large diffs are not rendered by default.
Oops, something went wrong.
53 changes: 11 additions & 42 deletions
53
abi-bindings/go/validator-manager/ExampleRewardCalculator/ExampleRewardCalculator.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
257 changes: 231 additions & 26 deletions
257
abi-bindings/go/validator-manager/NativeTokenStakingManager/NativeTokenStakingManager.go
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think with the current implementation, it would make more sense to keep all the uptime checks in the calculator. If the calculator returns 0, we don't release any rewards which is totally fine.