display genesis

[q9f]

the dora explorer does a good job displaying the consensus slot with the execution payload

https://dora-holesky.pk910.de/slot/2

however, it does not do it for genesis. the structure should be the same though?

https://dora-holesky.pk910.de/slot/0

[pk910]

Heya @q9f,

Sorry for late reaction, I've actually been looking into it a few times, but didn't find a proper solution for it yet.

The problem is basically that CL clients do not seem to be returning the correct execution payload for the genesis block:

$ curl -s http://10.16.97.4:5052/eth/v2/beacon/blocks/genesis | jq ".data.message.body.execution_payload"
{
  "parent_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "fee_recipient": "0x0000000000000000000000000000000000000000",
  "state_root": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "receipts_root": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "logs_bloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
  "prev_randao": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "block_number": "0",
  "gas_limit": "0",
  "gas_used": "0",
  "timestamp": "0",
  "extra_data": "0x",
  "base_fee_per_gas": "0",
  "block_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "transactions": [],
  "withdrawals": []
}

[q9f]

Interesting. My first reaction is to hardcode the genesis payload to be always EL block number #0 but then realizing that is not always the case.

My second thought is that might be interesting to implement in the CL clients but then again - most genesis won't have a payload at all - so Dora might be actually correct not showing anything.

Question remaining:

• if we "merge from genesis" as we did at Holesky, should the CL genesis be linked to the EL genesis payload? (probably a question for the core devs)
• would it be sensible to have a separate "EL blocks" view on Dora? (similar to what Etherscan/Beaconcha.in does)