Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This centralizes all crypto handling in crypto.nim instead of having it sprawled out.
In particular, for REST and RPC, pubkeys are supplied by users and due to lazy validation, those are unchecked (no check that they are infnity, on curve or in subgroup).
Fortunately:
Alternative: since RPC is scheduled for deprecation, we can also deleted the related files instead of merging this PR.
Regarding REST, validators pubkeys go through ValidatorIdent and/or
node.restKeysCache
and those are compared to the known validators key before use so no issue there:nimbus-eth2/beacon_chain/rpc/rest_beacon_api.nim
Lines 339 to 362 in 13b264d
Closes #1715