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

Deal with misleading storage rewards in Inflation struct #10092

Closed
mvines opened this issue May 17, 2020 · 4 comments · Fixed by #10309
Closed

Deal with misleading storage rewards in Inflation struct #10092

mvines opened this issue May 17, 2020 · 4 comments · Fixed by #10309
Milestone

Comments

@mvines
Copy link
Member

mvines commented May 17, 2020

This field is now dead code

/// Percentage of total inflation allocated to storage rewards
pub storage: f64,

as of #9992.

Removing it entirely would likely cause a snapshot ABI change, so renaming it to __unused would be an alternative. It should be removed from the getInflation RPC API AS well

@CriesofCarrots
Copy link
Contributor

CriesofCarrots commented May 27, 2020

Storage should also be removed from this calculation as well, correct?

self.total(year) - self.storage(year) - self.foundation(year)

Right now, in epochs after the foundation term:

  • total inflation = 0.015
  • validator inflation = 0.0135
    ...due to this

@mvines
Copy link
Member Author

mvines commented May 27, 2020

Yeah. Might need @ericlwilliams's help

@ryoqun
Copy link
Member

ryoqun commented May 27, 2020

Removing it entirely would likely cause a snapshot ABI change, so renaming it to __unused would be an alternative. It should be removed from the getInflation RPC API AS well

Hm, snapshot 1.3 should remove these fields at once, then? :)

@ericlwilliams
Copy link
Contributor

Yeah seems like that can/should be killed. Unless @aeyakovenko, or anyone else, sees Archivers on the horizon. For the foreseeable future, inflation should be divvied out just between validators and Foundation/Grant pools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants