GET
/
{apiKey}
/
eth
/
v1
/
beacon
/
genesis
Genesis data
curl --request GET \
  --url https://beacon-nd-422-757-666.p2pify.com/{apiKey}/eth/v1/beacon/genesis
{
  "data": {
    "genesis_time": "2025-03-21T15:09:52.470Z",
    "genesis_validators_root": "string",
    "genesis_fork_version": "string"
  }
}

​
Genesis data

GET https://beacon-nd-422-757-666.p2pify.com/{apiKey}/eth/v1/beacon/genesis
Developers can use this method to ensure they are interacting with the correct version of the Ethereum Beacon Chain and synchronize with the network.

​
Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • none

​
Response

  • object — genesis information.
    • genesis_time — the UNIX timestamp of when the Beacon Chain’s genesis event occurred. This is important because it marks the starting point of the Ethereum Beacon Chain network.
    • genesis_validators_root — the Merkle root of the initial set of validators at the time of the genesis event. Validators are participants in the PoS system that propose and attest to new blocks.
    • genesis_fork_version — the fork version of the Ethereum protocol active during the genesis event. This helps clients understand the version of the network they are interacting with.

​
200

Beacon genesis information successfully retrieved
​
data
object
required
​
genesis_time
date-time
required
The genesis time as an ISO 8601 formatted string.
​
genesis_validators_root
string
required
The 32-byte genesis validators root as a hex string.
​
genesis_fork_version
string
required
The 4-byte genesis fork version as a hex string.

​
500

Internal server error
​
code
integer
required
​
message
string
required
{
  "data": {
    "genesis_time": "2025-03-21T15:09:52.470Z",
    "genesis_validators_root": "string",
    "genesis_fork_version": "string"
  }
}