ed002cea7e
evidence: introduction of LightClientAttackEvidence and refactor of evidence lifecycle ( #5361 )
evidence: modify evidence types (#5342 )
light: detect light client attacks (#5344 )
evidence: refactor evidence pool (#5345 )
abci: application evidence prepared by evidence pool (#5354 )
4 years ago
710a97d850
evidence: remove amnesia & POLC ( #5319 )
## Description
remove unneeded types
ref #5288
4 years ago
b7f6e47a42
evidence: modularise evidence by moving verification function into evidence package ( #5234 )
4 years ago
65d7ce9c9c
evidence: improve amnesia evidence handling ( #5003 )
fix bug so that PotentialAmnesiaEvidence is being gossiped
handle inbound amnesia evidence correctly
add method to check if potential amnesia evidence is on trial
fix a bug with the height when we upgrade to amnesia evidence
change evidence to using just pointers.
More logging in the evidence module
Co-authored-by: Marko <marbar3778@yahoo.com>
5 years ago
dedf0d2350
proto: folder structure adhere to buf ( #5025 )
5 years ago
d54de61bf6
consensus: proto migration ( #4984 )
## Description
migrate consensus to protobuf
Closes: #XXX
5 years ago
7a8224f8a3
state: proto migration ( #4972 )
## Description
the second part of state proto migration
Closes: #XXX
5 years ago
26bea83694
evidence: retrieve header at height of evidence for validation ( #4870 )
validation of lunatic evidence requires that the node retrieve the header at the height of the infringement from the block store for comparison
5 years ago
7cb3d90e01
evidence: create proof of lock change and implement it in evidence store ( #4746 )
creates a proof of lock change which is an array of votes that proves the validator was permitted to change locked block and vote again. This proof is stored in the evidence pool and is used as a part of amnesia evidence
5 years ago
a620e5fd96
evidence: cap evidence to an absolute number ( #4780 )
The number of evidence that can be committed in a single block is capped by a new evidence parameter called MaxNum
5 years ago
52784f67d0
mempool: allow ReapX and CheckTx functions to run in parallel
allow ReapX and CheckTx functions to run in parallel, making it not possible to block certain proposers from creating a new block.
Closes : #2972
5 years ago
f6435f2c73
consensus: add comment as to why use mocks during replay ( #4785 )
Closes #4766
5 years ago
Callum Waters
Marko
Anton Kaliaev
