-
Notifications
You must be signed in to change notification settings - Fork 316
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
distributions: implement pool budget #5025
Comments
TalDerei
added a commit
that referenced
this issue
Jan 30, 2025
## Describe your changes Implements the LQT rewards comprising the total reward pool size for an epoch. ## Issue ticket number and link references #5025 ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > adds new logic for computing LQT issuance
conorsch
pushed a commit
that referenced
this issue
Jan 31, 2025
## Describe your changes Implements the LQT rewards comprising the total reward pool size for an epoch. ## Issue ticket number and link references #5025 ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > adds new logic for computing LQT issuance
conorsch
pushed a commit
that referenced
this issue
Feb 4, 2025
## Describe your changes Implements the LQT rewards comprising the total reward pool size for an epoch. ## Issue ticket number and link references #5025 ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > adds new logic for computing LQT issuance
conorsch
pushed a commit
that referenced
this issue
Feb 5, 2025
## Describe your changes Implements the LQT rewards comprising the total reward pool size for an epoch. ## Issue ticket number and link references #5025 ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > adds new logic for computing LQT issuance
conorsch
pushed a commit
that referenced
this issue
Feb 5, 2025
## Describe your changes Implements the LQT rewards comprising the total reward pool size for an epoch. ## Issue ticket number and link references #5025 ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > adds new logic for computing LQT issuance
conorsch
pushed a commit
that referenced
this issue
Feb 14, 2025
## Describe your changes Implements the LQT rewards comprising the total reward pool size for an epoch. ## Issue ticket number and link references #5025 ## Checklist before requesting a review - [x] I have added guiding text to explain how a reviewer should test these changes. - [x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: > adds new logic for computing LQT issuance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The distribution component defines an
EpochHandler
extension trait, with anend_epoch
method. This handler is triggered at the end of an epoch and executes the following logic:The pool size expands or contract based on how long the epoch lasts. Since epochs are at most ~2 days, this gives a predictable upper bound on the total issued rewards. On the other hand, since the pool size contracts with epoch length, this means that there’s no upside to trying to make the chain churn epochs.
The text was updated successfully, but these errors were encountered: