Delete Keys.

DELETE 
/eth/v1/keystores

DELETE must delete all keys from request.pubkeys that are known to the keymanager and exist in its persistent storage. Additionally, DELETE must fetch the slashing protection data for the requested keys from persistent storage, which must be retained (and not deleted) after the response has been sent. Therefore in the case of two identical delete requests being made, both will have access to slashing protection data.

In a single atomic sequential operation the keymanager must:

1. Guarantee that key(s) can not produce any more signature; only then
2. Delete key(s) and serialize its associated slashing protection data

DELETE should never return a 404 response, even if all pubkeys from request.pubkeys have no extant keystores nor slashing protection data.

Request

Responses

200

Success response

400

Bad request. Request was malformed and could not be processed

401

Unauthorized, no token is found

403

Forbidden, a token is found but is invalid

500

Internal server error. The server encountered an unexpected error indicative of a serious fault in the system, or a bug.