5de00b7ee8
## 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>
18 lines
420 B
Rust
18 lines
420 B
Rust
#[macro_use]
|
|
extern crate lazy_static;
|
|
|
|
mod block_cache;
|
|
mod deposit_cache;
|
|
mod inner;
|
|
mod metrics;
|
|
mod service;
|
|
|
|
pub use block_cache::{BlockCache, Eth1Block};
|
|
pub use deposit_cache::DepositCache;
|
|
pub use execution_layer::http::deposit_log::DepositLog;
|
|
pub use inner::SszEth1Cache;
|
|
pub use service::{
|
|
BlockCacheUpdateOutcome, Config, DepositCacheUpdateOutcome, Error, Eth1Endpoint, Service,
|
|
DEFAULT_CHAIN_ID,
|
|
};
|