Skip to main content
Version: next 🚧

DV Exit

These endpoints store and serve the partial exit signatures that charon exit and lido-dv-exit submit.

The cluster lock must be published first

The API only stores partial exits for clusters whose cluster lock has been published to it. charon dkg --publish publishes the lock; otherwise publish it by POSTing cluster-lock.json to /v1/lock (see Publish the cluster lock first).

Posting partial exits for a lock that isn't published returns 404 with the message cluster lock is not found: <lockHash> is not published to this API, and nothing is stored.

  • The exit status endpoints return 404 for a lock hash the API doesn't know.
  • The exit status endpoint is paginated with page and limit; limit is clamped to 1–100.
  • See Errors & Rate Limits for the error format and how to handle 429 responses.
GET/v1/exp/exit/{lockHash}/{shareIdx}/{validatorPubkey}Retrieve Distributed Validator threshold aggregated signed exit msg GET/v1/exp/exit/status/{lockHash}Retrieve validators exit status GET/v1/exp/exit/status/summary/{lockHash}Retrieve validators exit status summary POST/v1/exp/partial_exits/{lockHash}Push Distributed Validator partial signed exit message