Author | SHA1 | Message | Date |
---|---|---|---|
Marko |
a88537bb88
|
ints: stricter numbers (#4939) | 5 years ago |
Marko |
7c576f02ab
|
keys: change to []bytes (#4950) | 5 years ago |
Marko |
99d88cbe2f
|
crypto: remove key suffixes (#4941)
## Description - remove keyname suffix from keys Closes: #2228 |
5 years ago |
Marko |
a5a84e11f1
|
evidence: remove pubkey from duplicate vote evidence
this pr brings over the removal of pubkey from duplicatevote evidence from proto-breakage ref #4580 |
5 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 |