lighthouse/validator_client/slashing_protection
Michael Sproul e961ff60b4 Implement standard keystore API (#2736)
## Issue Addressed

Implements the standard key manager API from https://ethereum.github.io/keymanager-APIs/, formerly https://github.com/ethereum/beacon-APIs/pull/151
Related to https://github.com/sigp/lighthouse/issues/2557

## Proposed Changes

- [x] Add all of the new endpoints from the standard API: GET, POST and DELETE.
- [x] Add a `validators.enabled` column to the slashing protection database to support atomic disable + export.
- [x] Add tests for all the common sequential accesses of the API
- [x] Add tests for interactions with remote signer validators
- [x] Add end-to-end tests for migration of validators from one VC to another
- [x] Implement the authentication scheme from the standard (token bearer auth)

## Additional Info

The `enabled` column in the validators SQL database is necessary to prevent a race condition when exporting slashing protection data. Without the slashing protection database having a way of knowing that a key has been disabled, a concurrent request to sign a message could insert a new record into the database. The `delete_concurrent_with_signing` test exercises this code path, and was indeed failing before the `enabled` column was added.

The validator client authentication has been modified from basic auth to bearer auth, with basic auth preserved for backwards compatibility.
2022-01-30 23:22:04 +00:00
..
migration-tests Implement standard keystore API (#2736) 2022-01-30 23:22:04 +00:00
src Implement standard keystore API (#2736) 2022-01-30 23:22:04 +00:00
tests Implement standard keystore API (#2736) 2022-01-30 23:22:04 +00:00
.gitignore Implement slashing protection interchange format (#1544) 2020-10-02 01:42:27 +00:00
Cargo.toml Implement standard keystore API (#2736) 2022-01-30 23:22:04 +00:00
Makefile Adjusting ARCHIVE_URL (#2892) 2022-01-07 05:32:34 +00:00