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

0x0 block hash issue leading to possible fork of the node #4788

Open

sophoah opened this issue Oct 31, 2024 · 0 comments

Contributor

sophoah commented Oct 31, 2024

Describe the bug

A block hash of 0x0 may occur under certain corner cases of the node operation.

For the case of a leader, it may lead to the node being forked and not able to participate into consensus.

Team has been able to reproduce the issue in localnet but depends a lot on resource usage

To Reproduce
Using a CPU/Memory stress tool

Steps to reproduce the behavior:

run localnet
use the stress tool

Expected behavior
no 0x0 hash should ever be used during consensus

Additional context
Add any other context about the problem here.

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