Part of #402 — follow-up to the app-wiring PR.
Scope
Fail fast at startup when the beacon node is on a different network than the cluster lock: after building the eth2 clients, fetch the BN fork schedule and error if it lacks the lock's fork version. Charon does this in configureEth2Client (app/app.go:1022-1053 at v1.7.1: "mismatch between lock file fork version and beacon node fork schedule").
Today a Pluto node pointed at a wrong-network BN starts, schedules duties, and silently fails its share in a mixed cluster until signatures fail — a cheap misconfiguration guard prevents that.
Dependencies
None.
Acceptance
- Wrong-network BN → startup error naming the lock fork version and the BN network; correct network unaffected.
- beaconmock-backed test for both paths.
Part of #402 — follow-up to the app-wiring PR.
Scope
Fail fast at startup when the beacon node is on a different network than the cluster lock: after building the eth2 clients, fetch the BN fork schedule and error if it lacks the lock's fork version. Charon does this in
configureEth2Client(app/app.go:1022-1053at v1.7.1: "mismatch between lock file fork version and beacon node fork schedule").Today a Pluto node pointed at a wrong-network BN starts, schedules duties, and silently fails its share in a mixed cluster until signatures fail — a cheap misconfiguration guard prevents that.
Dependencies
None.
Acceptance