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

algod API for ConsensusParams #143

Closed
Vervious opened this issue Jul 11, 2019 · 1 comment · Fixed by #145
Closed

algod API for ConsensusParams #143

Vervious opened this issue Jul 11, 2019 · 1 comment · Fixed by #145
Assignees

Comments

@Vervious
Copy link
Contributor

Vervious commented Jul 11, 2019

(copied)
It would be nice to make ConsensusParams available by API so that client libraries don't have to maintain a parallel copy to what is maintained in Go code.

/v1/consensusparams could return current version
/v1/consensusparams/{escaped version} a specific version

OR

The precise need that prompted this was wanting to see MinTxnFee in APIs related to transaction fees where suggested fee was 1 which was well below the actual MinTxnFee. So maybe we just need that.

@Vervious Vervious added new-feature-request Feature request that needs triage 1 Enhancement and removed new-feature-request Feature request that needs triage labels Jul 11, 2019
@Vervious Vervious self-assigned this Jul 11, 2019
@Vervious
Copy link
Contributor Author

Added MiNTxnFee optional field to json structure returned by /v1/consensusparams/

derbear pushed a commit to derbear/go-algorand that referenced this issue Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant