feat: utilize split in existing rewards calculation #117
Conversation
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
seanmcgary
reviewed
Nov 25, 2024
seanmcgary
reviewed
Nov 25, 2024
seanmcgary
reviewed
Nov 25, 2024
seanmcgary
requested changes
Nov 25, 2024
0xrajath
force-pushed
the
release/rewards-v2
branch
from
d47aef9 to
5ebadaf
Compare
0xrajath
force-pushed
the
rajath/rewards-calculation
branch
from
f5ce3ef to
9f16817
Compare
ypatil12
reviewed
Dec 2, 2024
ypatil12
previously approved these changes
Dec 2, 2024
seanmcgary
dismissed
ypatil12’s stale review
The merge-base changed after approval.
seanmcgary
force-pushed
the
release/rewards-v2
branch
2 times, most recently
from
eb636fa to
883e248
Compare
0xrajath
force-pushed
the
rajath/rewards-calculation
branch
from
9f16817 to
f4572a6
Compare
seanmcgary
reviewed
Dec 2, 2024
seanmcgary
approved these changes
Dec 2, 2024
seanmcgary
pushed a commit
that referenced
this pull request
Dec 3, 2024
Utilize the `OperatorAVSSplit` and `OperatorPISplit` in the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).
seanmcgary
pushed a commit
that referenced
this pull request
Dec 5, 2024
Utilize the `OperatorAVSSplit` and `OperatorPISplit` in the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).
seanmcgary
pushed a commit
that referenced
this pull request
Dec 6, 2024
Utilize the `OperatorAVSSplit` and `OperatorPISplit` in the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).
seanmcgary
pushed a commit
that referenced
this pull request
Dec 11, 2024
Utilize the `OperatorAVSSplit` and `OperatorPISplit` in the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).
seanmcgary
pushed a commit
that referenced
this pull request
Dec 12, 2024
Utilize the `OperatorAVSSplit` and `OperatorPISplit` in the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).
seanmcgary
pushed a commit
that referenced
this pull request
Dec 12, 2024
Utilize the `OperatorAVSSplit` and `OperatorPISplit` in the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).
seanmcgary
pushed a commit
that referenced
this pull request
Dec 12, 2024
Utilize the `OperatorAVSSplit` and `OperatorPISplit` in the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Utilize the
OperatorAVSSplitandOperatorPISplitin the existing rewards v1 and Programmatic incentives calculation (instead of the hardcoded 10% split).