tendermint

8165 Commits

183 Branches

291 MiB

Tree: f66b7a8e32

Commit Graph

Author	SHA1	Message	Date
Callum Waters	3c21c3546c	evidence: remove phantom validator evidence (#5181 )	4 years ago
Anton Kaliaev	41c11ad2c1	evidence: handling evidence from light client(s) (#4532 ) Closes: #4530 This PR contains logic for both submitting an evidence by the light client (lite2 package) and receiving it on the Tendermint side (/broadcast_evidence RPC and/or EvidenceReactor#Receive). Upon receiving the ConflictingHeadersEvidence (introduced by this PR), the Tendermint validates it, then breaks it down into smaller pieces (DuplicateVoteEvidence, LunaticValidatorEvidence, PhantomValidatorEvidence, PotentialAmnesiaEvidence). Afterwards, each piece of evidence is verified against the state of the full node and added to the pool, from which it's reaped upon block creation. * rpc/client: do not pass height param if height ptr is nil * rpc/core: validate incoming evidence! * only accept ConflictingHeadersEvidence if one of the headers is committed from this full node's perspective This simplifies the code. Plus, if there are multiple forks, we'll likely to receive multiple ConflictingHeadersEvidence anyway. * swap CommitSig with Vote in LunaticValidatorEvidence Vote is needed to validate signature * no need to embed client http is a provider and should not be used as a client	5 years ago
Anton Kaliaev	4936b23dae	adr-047: evidence handling (#4429 ) Closes #4213 and #4182	5 years ago

Author

SHA1

Message

Date

Callum Waters

3c21c3546c

evidence: remove phantom validator evidence (#5181 )

4 years ago

Anton Kaliaev

41c11ad2c1

evidence: handling evidence from light client(s) (#4532 )

Closes: #4530

This PR contains logic for both submitting an evidence by the light client (lite2 package) and receiving it on the Tendermint side (/broadcast_evidence RPC and/or EvidenceReactor#Receive). Upon receiving the ConflictingHeadersEvidence (introduced by this PR), the Tendermint validates it, then breaks it down into smaller pieces (DuplicateVoteEvidence, LunaticValidatorEvidence, PhantomValidatorEvidence, PotentialAmnesiaEvidence). Afterwards, each piece of evidence is verified against the state of the full node and added to the pool, from which it's reaped upon block creation.

* rpc/client: do not pass height param if height ptr is nil

* rpc/core: validate incoming evidence!

* only accept ConflictingHeadersEvidence if one

of the headers is committed from this full node's perspective

This simplifies the code. Plus, if there are multiple forks, we'll
likely to receive multiple ConflictingHeadersEvidence anyway.

* swap CommitSig with Vote in LunaticValidatorEvidence

Vote is needed to validate signature

* no need to embed client

http is a provider and should not be used as a client

5 years ago

Anton Kaliaev

4936b23dae

adr-047: evidence handling (#4429 )

Closes #4213 and #4182

5 years ago

3 Commits (f66b7a8e321630cf95296cad6c8fa3b1c33b0016)