-
Notifications
You must be signed in to change notification settings - Fork 80
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
Move partial signature verification to parsigdb #217
Comments
Note this is a security feature, assuming Byzantium/unexpected behaviour from peers. This could be moved out to V1 milestone. |
Note we should probably do verification in parsigex and validagtorAPI, as close to the source as possible (fail fast). Only doing this in parsigdb results in invalid "events" being generated and complicated |
Note verification in DKG and Charon Run is different. Will need to pass in the verification function as param to |
Adds NewVerifyFunc in eth2util/signing. category: refactor ticket: #217
Adds verifyFunc to Validatorapi component and removes old methods. category: refactor ticket: #217
Adds verification functions for each duty in eth2util/signing and use them in validatorapi. category: refactor ticket: #217
Adds verification function to parsigex and related constructors for verifyFunc: NewEth2Verifier and newDKGVerifier. category: feature ticket: #217
Adds partial signature verification before aggregation. category: refactor ticket: #217
Problem to solve
We currently verify partial signatures submitted by the VC in the validatorapi. This doesn't prevent invalid signatures being added by our peers.
Proposed solution
VerifyFunc
to parsigDB.type VerifyFunc func(ctx context.Context, duty core.Duty, pubkey core.PubKey, parSig core.ParSignedData) error
validatorapi
and move toeth2util/signing
, providing aVeirfy(...) error
funciton.Varify
function that can do lockhash and depositdata verifucation based on custom duty types.The text was updated successfully, but these errors were encountered: