e961ff60b4
## 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.
15 lines
456 B
TOML
15 lines
456 B
TOML
[package]
|
|
name = "eth2_serde_utils"
|
|
version = "0.1.1"
|
|
authors = ["Paul Hauner <paul@paulhauner.com", "Michael Sproul <michael@sigmaprime.io>"]
|
|
edition = "2018"
|
|
description = "Serialization and deserialization utilities useful for JSON representations of Ethereum 2.0 types."
|
|
license = "Apache-2.0"
|
|
|
|
[dependencies]
|
|
serde = { version = "1.0.116", features = ["derive"] }
|
|
serde_derive = "1.0.116"
|
|
serde_json = "1.0.58"
|
|
hex = "0.4.2"
|
|
ethereum-types = "0.12.1"
|