Activation queue breakdown

Extraits de code

curl "https://api.oanor.com/ethstakingqueue-api/v1/entry" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/ethstakingqueue-api/v1/entry", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/ethstakingqueue-api/v1/entry");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/ethstakingqueue-api/v1/entry",
    headers={"x-oanor-key": "oanor_test_..."}
)

Exemple de réponse

Une réponse réelle de ce endpoint, capturée lors du dernier contrôle de santé.

{
    "data": {
        "note": "The Ethereum activation (entry) queue. eligible_and_churning are validators past the eligibility delay and being admitted at the churn limit; deposited_not_yet_eligible were just deposited and still wait out the eligibility delay before joining the churn. earliest/latest_activation_epoch come straight from the validator records. est_clear_hours estimates how long the queued ETH takes to activate at the current churn limit of 256 ETH/epoch. Live, cached ~90s.",
        "epoch": 454431,
        "source": "Ethereum Beacon API (ethereum-beacon-api.publicnode.com), keyless",
        "eth_waiting": 4663.26,
        "est_clear_hours": 1.9,
        "validators_waiting": 3062,
        "eligible_and_churning": {
            "eth": 1426.26,
            "validators": 11,
            "latest_activation_epoch": 454433,
            "earliest_activation_time": "2026-06-13T04:45:11.000Z",
            "earliest_activation_epoch": 454432
        },
        "churn_limit_eth_per_epoch": 256,
        "deposited_not_yet_eligible": {
            "eth": 3237,
            "validators": 3051
        }
    },
    "meta": {
        "timestamp": "2026-06-13T04:42:42.934Z",
        "request_id": "6c896ab2-08c0-486c-b53c-f2b578f4cbdc"
    },
    "status": "ok",
    "message": "Entry queue retrieved successfully",
    "success": true
}