The lifecycle of an ETH validator (click to expand)

Statuses description

Status	Description	Action Needed
`provisioned`	A validator has been created by Figment and is available for funding.	Get a funding transaction
`deposited_not_finalized`	We have detected a deposit transaction on the EL but it hasn't been finalized	Nothing ⏳ ~ 20 minutes
`deposited`	We have detected a deposit transaction and we consider it finalized but the validator is not in the activation queue yet.	Nothing ⏳ ~ 13 minutes
`pending_queued`	The validator is in the activation queue.	Nothing ⏳ ~ 37 days (as of July 2023)
`active_ongoing`	The validator is in the active set and earning rewards
`active_exiting`	The validator has requested to exit the active set but is still earning rewards	⏳ ~ 1 day (as of July 2023)
`active_slashed`	The validator is still part of the active set but has been slashed. It cannot earn rewards or perform a voluntary exit.
`exited_unslashed`	The validator has no slashing penalties and has voluntarily exited the active set. This occurs when making a full withdrawal.	Exactly 256 epochs (~ 27.3h)
`exited_slashed`	The validator has been removed from the active set and has slashing penalties.	Exactly 2^13 epochs (~36 days)
`withdrawal_possible`	The validator has exited the active set and a withdrawal can be performed. Waiting on the sweep.	⏳ ~ 5 days (as of July 2023)
`withdrawal_done`	The full withdrawal of the deposited 32 ETH to the withdrawal address has been completed

Where to find status

Our endpoint GET /validators returns validator metadata, among which are the 3 fields: status, status_synced_at and status_history

{
  "type": "validator",
    "attributes": {
	  // pub key, withdrawal credentials, deposit data root, etc
      "status": "deposited",
      "status_synced_at": "2023-02-03T15:00:21.420Z",
      "status_history": [
        {
          "status": "funding_requested",
          "changed_at": "2023-01-04T16:00:14.459Z"
        }
      ],
      // more attributes
}