Adding additional GRPC endpoints for block explorer #1922
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added constants grpc endpoint Added block size grpc call Added block fee endpoint Added version response Added GetTokensInCirculation RPC call Added network difficulty Added estimated hashrate to difficulty response Return array of values for size and fee Some cleanup
Krakaw
force-pushed
the
krakaw-additional-base-stats
branch
from
7e4b573 to
e629046
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The following endpoints have been added to the GRPC service based on the core requirements.
I've used the standard local
LocalNodeCommsInterfaceto extract all of the data used in these responses, it will probably be faster to use an instance ofasync_dband even faster once thepostgres_backendbranch is in to build more of these metrics directly into the db.I wanted to get this up in the mean time, but GetBlockSize and GetBlockFees still need to have their quartile and quantile implementations created which is why their response type is an array of double.
Motivation and Context
We required more stats from the base node for the block explorer.
How Has This Been Tested?
cargo testTypes of changes
Checklist:
developmentbranch.cargo-fmt --allbefore pushing.