fix proposal execution head at genesis; rm non-spec SSE; ensure envelopse SSE has envelope in database

[tersec]

For the proposal head at genesis, even though

• Treat genesis block as empty payload parent ethereum/consensus-specs#5067

states

        state.latest_block_hash = spec.Hash32()
        empty_requests_root = spec.hash_tree_root(spec.ExecutionRequests())
        state.latest_execution_payload_bid = spec.ExecutionPayloadBid(
            block_hash=spec.Hash32(eth1_block_hash),

the current generator does the opposite of this. So, work around this mismatch.

Should be removed when the generator is fixed.

According to https://github.com/ethereum/beacon-APIs/blob/v5.0.0-alpha.1/apis/eventstream/index.yaml execution_payload_available and execution_payload_bid exist but plain execution_payload does not.

[github-actions]

Unit Test Results

       12 files  ±0    2 816 suites  ±0   1h 16m 1s ⏱️ - 5m 2s
15 853 tests ±0  14 288 ✔️ ±0  1 565 💤 ±0  0 ❌ ±0 
76 516 runs  ±0  74 776 ✔️ ±0  1 740 💤 ±0  0 ❌ ±0 

Results for commit 1f7e493. ± Comparison against base commit c796b98.

[ahshum]

Is the eventstream topic causing the issue? Yes it is right that the topics not exists because the beacon-API PR has not been merged yet #8183

But seems that other clients have merged the changes according to the references in the beacon-API PR.

[tersec]

Is the eventstream topic causing the issue? Yes it is right that the topics not exists because the beacon-API PR has not been merged yet #8183

But seems that other clients have merged the changes according to the references in the beacon-API PR.

Ah,

• Add execution_payload and execution_payload_gossip event ethereum/beacon-APIs#588

merged 4 hours ago, after I opened this PR and enabled auto-merge.

It wasn't per se causing problems, no, but when I was looking into where to put the onEnvelopeAvailable callback, it proved redundant, and at the time, it was... not in specs.

It can be added back, in the correct place.

[alialobidm]

``

[alialobidm]