mirror of
https://gitlab.com/pulsechaincom/lighthouse-pulse.git
synced 2025-01-10 13:01:22 +00:00
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>
10 lines
307 B
Rust
10 lines
307 B
Rust
mod common;
|
|
mod eth1_genesis_service;
|
|
mod interop;
|
|
|
|
pub use eth1::Config as Eth1Config;
|
|
pub use eth1::Eth1Endpoint;
|
|
pub use eth1_genesis_service::{Eth1GenesisService, Statistics};
|
|
pub use interop::{interop_genesis_state, DEFAULT_ETH1_BLOCK_HASH};
|
|
pub use types::test_utils::generate_deterministic_keypairs;
|