-
**Describe the bug**
The node throws this error message
```
panic: precommit step; +2/3 prevoted for an invalid block: wrong Block.Header.AppHash. Expected 44E33FF1736A0144C1B8BC906812802A0E03C2E3…
-
## Summary of Bug
I have just cloned and built provenanced and am attempting to join the testnet network. On start I get a SIGSEGV crash. I'm not sure if this is the correct place to report…
-
I believe the current assumption is that there is a signature from the submitter that is used to gate these updates. We would also like to be able to support Proof of Consensus (for e.g. tendermint), …
-
I observed this only when enabling the CAT mempool, when using 134MB blocks:
> 4:15PM ERR CONSENSUS FAILURE!!! err="runtime error: invalid memory address or nil pointer dereference" module=consensu…
-
Upon client expiry and misbehaviour, we allow governance or an approved authority to substitute the invalid client with a subsitute client.
In the tendermint client, we copy over all the consensus …
-
This can easily starve sub-futures if not handled carefully.
-
Version: v1.0.11-hardfork
One of two Cronos Mainnet nodes stopped getting new blocks after 12089664. It got:
> 6:17AM ERR prevote step: ProposalBlock is invalid err="wrong Block.Header.AppHash. …
-
This warning in smoke tests in the node needs to be investigated as the underlying issue could trigger a consensus failure
This appears to happen when certain txs are sent to the node during smoke …
-
Please compare it with
https://github.com/tendermint/tendermint/wiki/Byzantine-Consensus-Algorithm
muf18 updated
6 years ago
-
## Implement Tendermint Consensus Compatible with Substrate
### Description
The goal of this issue is to implement the Tendermint consensus algorithm in a way that is compatible with the Substra…