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.

Sign up for GitHub

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

Jump to bottom

bug in hotstuff consensus latency logic #12

Open

namn-grg opened this issue Apr 4, 2024 · 1 comment

Collaborator

namn-grg commented Apr 4, 2024

Consensus latency for the hotstuff sometimes comes out to be negative which is not possible

and the other times the value is very less - between 1-5ms which also should not be the case

Collaborator Author

namn-grg commented Apr 8, 2024

2 bugs identified -

Logs of 2 diff nodes have time difference. If a block is created in node-0 and committed in node-1 then the logs of node-1 shows the committed time before the creation time in node-0
Sometimes the hash comes out to be the same. Discussed with Alberto he said - the hash in the logs is partial and not the full hash so there are chances

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment