Genesis time, network age and slot/epoch constants

Frammenti di codice

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

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

$ch = curl_init("https://api.oanor.com/beaconchain-api/v1/genesis");
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/beaconchain-api/v1/genesis",
    headers={"x-oanor-key": "oanor_test_..."}
)

Risposta di esempio

Una risposta reale di questo endpoint, acquisita dall'ultimo health check.

{
    "data": {
        "note": "The Beacon Chain's genesis and timing constants. The proof-of-stake beacon chain went live on 1 December 2020; network_age shows how long it has been running. Ethereum runs on a fixed clock: a slot every 12 seconds, 32 slots per epoch (so an epoch every 384 seconds ≈ 6.4 minutes) — the constants every consensus calculation uses. Cached ~daily.",
        "source": "public Ethereum consensus-layer (Beacon) API, keyless",
        "genesis_time": "2020-12-01T12:00:23.000Z",
        "slots_per_epoch": 32,
        "network_age_days": 2019.7,
        "seconds_per_slot": 12,
        "genesis_time_unix": 1606824023,
        "network_age_years": 5.53,
        "seconds_per_epoch": 384,
        "genesis_fork_version": "0x00000000"
    },
    "meta": {
        "timestamp": "2026-06-13T04:42:53.715Z",
        "request_id": "d1155f58-9462-48af-b639-679e7a5ad43f"
    },
    "status": "ok",
    "message": "Genesis retrieved successfully",
    "success": true
}