Skip to content

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

Open
@sophoah

Description

@sophoah

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:

  1. run localnet
  2. 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions