-
Notifications
You must be signed in to change notification settings - Fork 704
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
Add L1 validator fees API #3647
Conversation
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.
suggestion to order the endpoints alphabetically #3648
Signed-off-by: Meaghan FitzGerald <[email protected]> Co-authored-by: Stephen Buttolph <[email protected]>
- Removed: | ||
- `info.GetTxFee` |
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.
was this affected by the rollback?
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.
No - that is unrelated to this PR
Co-authored-by: Meaghan FitzGerald <[email protected]> Signed-off-by: Stephen Buttolph <[email protected]>
Co-authored-by: Meaghan FitzGerald <[email protected]> Signed-off-by: Stephen Buttolph <[email protected]>
Why this should be merged
Currently it is difficult to learn what the current fee is for L1 validators.
How this works
Adds APIs:
platform.getValidatorFeeConfig
platform.getValidatorFeeState
It was decided against modifying the existing APIs
platform.getFeeConfig
andplatform.getFeeState
because that would have made the types more complex.How this was tested
Added unit tests similar to
platform.getFeeConfig
andplatform.getFeeState
.Need to be documented in RELEASES.md?
Documented the new APIs in both
service.md
andRELEASES.md
.