Repository navigation
feat: add geth and nethermind nodes to heze-devnet-3 - #12
Conversation
![redpandabot[bot]](https://avatars.githubusercontent.com/in/3749543?s=60&v=4){kind=small}
There was a problem hiding this comment.
Adds one geth and one nethermind node per CL to heze-devnet-3 with validator ranges 1600–2400 and bumps both EL images to their heze-devnet-3 tags. Validator ranges are disjoint and pass the existing terraform validation, the cl-el node naming matches the established devnet-2 pattern, and per-EL ansible group_vars already reference the bumped image keys. Nothing wrong found.
Reviewed 2 changed file(s) @ 4af18583 — no blocking issues found.
"Move fast and break things." — Mark Zuckerberg (early)
There was a problem hiding this comment.
Summary
Adds one geth and one nethermind node per CL client to heze-devnet-3 (inventory, terraform, all tooling endpoints) and bumps the geth/nethermind images to heze-devnet-3. The config is internally consistent — validator ranges 1600–2400 match between terraform and inventory, and every tooling values file lists the new nodes. One omission: the two new lighthouse-backed nodes are missing from all published peer metadata.
Issues
- 🟡
network-configs/devnet-3/metadata/enodes.txt:16— lighthouse-geth-1 and lighthouse-nethermind-1 missing from peer metadata — see the thread on that line
Reviewed @ 737c84a2
"Move fast and break things." — Mark Zuckerberg (early)
| enode://071b89b36e5122b9256afb1d330f82c1c05c48f7ed8e47eb776c6f4a73b75e4c4a2be4db0a5a22cdb7ed6f09528cf27e945fbf6017c64394dbacfae81a47218b@138.197.45.75:30303?discport=30303 No newline at end of file | ||
| enode://071b89b36e5122b9256afb1d330f82c1c05c48f7ed8e47eb776c6f4a73b75e4c4a2be4db0a5a22cdb7ed6f09528cf27e945fbf6017c64394dbacfae81a47218b@138.197.45.75:30303?discport=30303 | ||
| enode://277532c34c6b0dc5b592f3ce7999b6965c2b47781471598fd917b42630627d105c603f5e0f49435401714a135feb4424f49647dfd2e3893f88af6872d57f91d6@167.71.87.174:30303?discport=30303 | ||
| enode://134f9a24b80c1e4ba797549865c19889ea7aa375a8616e2007352db755a73e0e71fe25fd2a3d4cfc27833d59b83b2973b2480e572487ca1ca60b687db8310fe0@209.38.240.118:30303?discport=30303 No newline at end of file |
There was a problem hiding this comment.
🟡 lighthouse-geth-1 and lighthouse-nethermind-1 missing from peer metadata
enodes.txt, el_enrs.txt and bootstrap_nodes.txt each gained entries for six of the eight new nodes, but nothing for lighthouse-geth-1 (143.110.223.221) or lighthouse-nethermind-1 (134.122.50.150) — I decoded every ENR's embedded IP to confirm. Master lists an entry for every EL node, so these two peers are invisible to anything consuming the published network config and rely purely on DHT discovery.
Adds one geth and one nethermind node per CL (teku, lodestar, lighthouse, prysm) to heze-devnet-3 and bumps geth and nethermind to their heze-devnet-3 images, which pass the heze hive suites apart from the not-yet-implemented EIP-8198 base fee cap and a geth BAL netting edge case, and went through the Gloas → Heze 12s → 9s transition in a local kurtosis run in sync with ethrex. The new nodes get validator keys 1600–2400, beyond the 1600 genesis validators, to be activated through deposits.