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

Accessing current View Change Number via RPC. #629

Closed
saltyskip opened this issue Mar 11, 2019 · 4 comments
Closed

Accessing current View Change Number via RPC. #629

saltyskip opened this issue Mar 11, 2019 · 4 comments

Comments

@saltyskip
Copy link

Is there a way to access what the current View Change Count is in a give block, as well as the total number of rounds necessary in a historical block via a method like RPC.

This would be useful for improved monitoring of the NEO blockchain, as well as being able to do analysis later on why certain blocks required many view changes

@vncoelho
Copy link
Member

vncoelho commented Mar 11, 2019

Hi Andrei, you can use a normal node and start consensus for monitoring messages.
We could design a plugin focused on that, in which a node would monitor follow messages and display. We could even try to do that completely in the frontend, if we were able to join the C# P2P protocol.

@vncoelho
Copy link
Member

#482 will probably help us in this task, @shargon told us that it was almost finished.

@igormcoelho
Copy link
Contributor

Andrei, the easiest way to do so, is by calculating the time taken by each block... around 15s is view 0, 30s view 1, 60s view 2, 120s view 3... and so on.
The actual view is never stored on the blockchain, because it's unnecessary for blockchain persistance, it's just part of the current BFT consensus protocol.

You can monitor every type of node messages on real-time by connecting your own node to the main network, so we could perhaps store this information for future usage... I don't think someone is currently publicly cataloguing this, but I agree this is nice information for analysis.

@saltyskip
Copy link
Author

Thanks guys this answers my question. I will close this issue

Thacryba pushed a commit to simplitech/neo that referenced this issue Feb 17, 2020
Thacryba pushed a commit to simplitech/neo that referenced this issue Feb 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants