-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: update ADR-005 with consumer double voting #1283
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the work! Couple of comments I believe should be addressed, but nothing particularly serious, so I'm approving!
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
referred to as [`infraction_block_header`](https://github.com/cosmos/interchain-security/blob/20b0e35a6d45111bd7bfeb6845417ba752c67c60/proto/interchain_security/ccv/provider/v1/tx.proto#L77). | ||
The latter will provide the malicious validator's public key and the chain ID required to verify the signature of the votes contained in the evidence. | ||
|
||
Note that double signing evidence will be verified by using the same conditions than in the CometBFT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not true. We are not checking the validator's power or the total power for example.
docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
Outdated
Show resolved
Hide resolved
which is used to slash the misbehaving validator. In the context of untrusted consumer chains, all their states, including vscIDs, | ||
could be corrupted and therefore cannot be used for slashing purposes. | ||
|
||
- For the same reasons explained above, the age of a consumer double signing evidence can't be verified, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this apply to only double signing evidence? Are we verifying the age of light client attack evidence?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC, the age of the light client attack evidence is verified when we call CheckMisbehaviourAndUpdateState, which checks that the conflicting headers in the LCA have a trusted state that isn't older than the unbonding period.
@insumity could you confirm this please?
Co-authored-by: Marius Poke <[email protected]>
* save draft * draft * save changes * first draft * typo * typo * last changes * change TM to Comet * fix date * fix links * address comments * add ADR link * change cometBFT and cosmos SDK refs to specific version * fix links * Update docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md Co-authored-by: Marius Poke <[email protected]> * update structure * save changes * rework double signing limitations * fix links * fix IBC links --------- Co-authored-by: Marius Poke <[email protected]> (cherry picked from commit 54e5220) # Conflicts: # docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md
* save draft * draft * save changes * first draft * typo * typo * last changes * change TM to Comet * fix date * fix links * address comments * add ADR link * change cometBFT and cosmos SDK refs to specific version * fix links * Update docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md Co-authored-by: Marius Poke <[email protected]> * update structure * save changes * rework double signing limitations * fix links * fix IBC links --------- Co-authored-by: Marius Poke <[email protected]>
Description
Closes: #1266
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
docs:
prefix in the PR titleReviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
docs:
prefix in the PR titlemake build-docs
)