-
Notifications
You must be signed in to change notification settings - Fork 217
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
Clarify the description of getNetworkParameters
in the API and CLI.
#1698
Clarify the description of getNetworkParameters
in the API and CLI.
#1698
Conversation
Make it clear that this command shows parameters for the current epoch.
Make it clear that this endpoint returns parameters for the current epoch.
bors r+ |
1698: Clarify the description of `getNetworkParameters` in the API and CLI. r=jonathanknowles a=jonathanknowles # Related Issues #1690 # Overview This PR clarifies the descriptions of the `getNetworkParameters` API endpoint and the associated `network parameters` CLI command, in response to [review feedback](https://github.com/input-output-hk/cardano-wallet/pull/1694/files#r431011565) for #1694, Co-authored-by: Jonathan Knowles <[email protected]>
bors r- |
Canceled |
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.
Actually ... technically those parameters which are returned are from genesis block because none of them are updatable. They will never change.
And also technically, suppose that there are updatable parameters in there. They will be for latest epoch which the node has synced, which is not necessarily the current epoch. Although I think it's an acceptable simplification to say "current epoch" in this context.
bors r+ |
Build succeeded |
Related Issues
#1690
Overview
This PR clarifies the descriptions of the
getNetworkParameters
API endpoint and the associatednetwork parameters
CLI command, in response to review feedback for #1694,