-
Notifications
You must be signed in to change notification settings - Fork 11
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
Include minutes per block statistics #1942
Comments
Just to make sure firstKeyblockTime is the block at height 1, right? |
Not super sure with it. Keyblock 0 does not have time set. |
Right now I'm using the block at height 1, is something like this ok?
|
I will think about the output format and let you know next week |
Please format the response in milliseconds. I am not sure about it, why the block 0 does not have any time entry? |
Forgot to give an update, I'm not sure why it's 0, but it's that way on the node aswell, so it should be ok to use height 1. The feature should be in the next release |
This has been deployed -> https://mainnet.aeternity.io/mdw/v3/stats |
Ok, cool! I would just expect the value to be named accordingly - milliseconds or mircro time to be consistent with mdw naming. Can you rename it, please? I haven't used it so far. What name do you suggest? |
Yeah, I seem to have missed it. How does |
I dont't have specific preference. You might use your naming convention. Afaik you use 'micro' prefix. Up to you |
please include value
blocks per minute to v3/stats
It should be around 3 minutes per block
The formula is fairly simple. This is how I count it on FE.
I believe you are already using this approximate value in your computations, so it should be easy to expose, right?
The text was updated successfully, but these errors were encountered: