lighthouse/beacon_node/eth1/src
Pawan Dhananjay 5de00b7ee8 Unify execution layer endpoints (#3214)
## Issue Addressed

Resolves #3069 

## Proposed Changes

Unify the `eth1-endpoints` and `execution-endpoints` flags in a backwards compatible way as described in https://github.com/sigp/lighthouse/issues/3069#issuecomment-1134219221

Users have 2 options:
1. Use multiple non auth execution endpoints for deposit processing pre-merge
2. Use a single jwt authenticated execution endpoint for both execution layer and deposit processing post merge

Related https://github.com/sigp/lighthouse/issues/3118

To enable jwt authenticated deposit processing, this PR removes the calls to `net_version` as the `net` namespace is not exposed in the auth server in execution clients. 
Moving away from using `networkId` is a good step in my opinion as it doesn't provide us with any added guarantees over `chainId`. See https://github.com/ethereum/consensus-specs/issues/2163 and https://github.com/sigp/lighthouse/issues/2115


Co-authored-by: Paul Hauner <paul@paulhauner.com>
2022-06-29 09:07:09 +00:00
..
block_cache.rs Return eth1-related data via the API (#1797) 2020-11-02 00:37:30 +00:00
deposit_cache.rs Unify execution layer endpoints (#3214) 2022-06-29 09:07:09 +00:00
inner.rs Implement SSZ union type (#2579) 2021-09-25 05:58:36 +00:00
lib.rs Unify execution layer endpoints (#3214) 2022-06-29 09:07:09 +00:00
metrics.rs Monitoring service api (#2251) 2021-05-26 05:58:41 +00:00
service.rs Unify execution layer endpoints (#3214) 2022-06-29 09:07:09 +00:00