Skip to content

Validating blocks failed after many restart for the master nodes [Bug] #16

@transhkoot

Description

@transhkoot

Describe the bug
Sometimes with no reason when restarting the node on the startup it discover that some of the block is not valid ( height or "transaction merkle hash" ) but the block is valid and the merkel hash tree is valid.
So the network start deleting all nodes( not sure why this behaves exists) it should be reconsidered. why you when you call to delete the invalid blocks you call for deleting of all accounts and delegate states?

check this blockManager.deleteByHeightIn(range.toList()) in BlockValidator
and this fun checkTransactionMerkleHash() in MainBlockValidator

To Reproduce
Steps to reproduce the behaviour:
I'm running 5 nodes 3 delegates and 2 peers on virtual machine. just run it for a while and try to restart it every while and you will see the error

Expected behavior
It must not delete any of the states

I know this project is dead but I posted it in hope someone could fix it or at least explain why this behaves like this

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