Repository navigation
Conversation
The Moksha bootnodes were migrated to discovery-only hosts (vana-node-ops moksha-bootnode-1/2: devp2p discv4 listen + prysm bootnode, UDP only). The example env still shipped the pre-migration records: - CL_BOOTNODE_1 was the old beacon-node ENR advertising tcp/13000, so Prysm dialed it and logged refused connections. - CL_BOOTNODE_2 predated fork-version pinning (digest f5a5fd42). - The third bootnode (34.56.57.89) no longer answers discv4 or discv5 and is not in the ops inventory. Replace both CL ENRs with the records the live bootnodes print at startup (same node IDs, udp 12000 only), remove the third EL/CL entries, and use the `:0?discport=30303` form for both enodes since neither runs an RLPx listener. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.env.moksha.examplestill carried the pre-migration Moksha bootnode records. Both bootnodes are now discovery-only hosts (devp2p discv4 listen+ Prysmbootnode, UDP only, managed in vana-node-ops asmoksha-bootnode-1/2), and the third bootnode is gone.CL_BOOTNODE_1was the old beacon-node ENR for 34.45.237.218 (seq 1733255857231). It advertised tcp/13000 and syncnets, so Prysm tried to dial it and logged refused connections. Replaced with the live record (seq 1789573682778, udp/12000 only). Same node IDe9398cae….CL_BOOTNODE_2predated fork-version pinning (digestf5a5fd42). Replaced with the live record for 34.57.71.47 (seq 1786550150287). Same node ID.CL_BOOTNODE_3and the thirdGETH_BOOTNODESenode) removed. It answers neither discv4 nor discv5, and vana-node-ops'moksha_published_bootnodeslists only bootnode-1/2.:30303to:0?discport=30303, matching the second entry. Neither bootnode runs an RLPx listener.Verification
docker logs bootnodeon each host; secp256k1 keys match the previous records byte for byte.Note
The bootnodes currently run with
--fork-version=20000089(genesis), so their eth2 field carries digeste693d2derather than the network's414ecbca(Deneb,0x20000093). Harmless for Prysm, which never dials records without a TCP port. If that flag is changed in vana-node-ops, the records change and this file needs a follow-up.🤖 Generated with Claude Code