protolambda

Got a 502 bad-gateway on yarn task of integration tests. Will re-run from failed when CI is done

@smartcontracts can you help answer the question above? Changes LGTM otherwise

``` Nov 28 22:14:40 protoalpha nimbus_beacon_node[63512]: WRN 2022-11-28 22:14:40.692+01:00 Eth1 chain monitoring failure, restarting topics="eth1" err="getBlockByHash(m.dataProvider,\n BlockHash(m.depositsChain.finalizedBlockHash.data)) failed 3 times. Last error: Parameter [result] expected JObject but got JNull" node=goerlinimbus...

Closing this issue, it seems stale. Please re-open if any issues persist. Also note that TS things are being moved to https://github.com/ethereum-optimism/ecosystem

Is this feature still being considered? This would make docker setups less painful to configure.

Any chance this feature can be implemented, now that the mainnet Dencun release is out of the way? I am still interested in being able to configure lighthouse this way.

Quick update about CI; I believe @sebastianst has a draft of invoking the transaction-trace on failure, to capture the `output`, and determine the error code, to fix the FP part...

Stale issue, closing this. The op-node by now does retry, and with backoff, and a maximum number of attempts.

Correction: it does retry, but only for L1 connection, not L2.

One key insight that I had after the initial draft, and which I am not sure I put put there on github, is that it can be implemented without merkleizing...