feat: add 2+3.relay.obol.dev to charon p2p relays (keep partners)#322
Merged
Conversation
…-party LCDVN's CHARON_P2P_RELAYS were drifting from the production nodeopco fleet config: - docker-compose.yml default only had 0+1.relay.obol.tech (missing 2.relay.obol.dev + 3.relay.obol.dev that were added recently) - .env.sample.mainnet/hoodi listed 0+1.relay.obol.tech and two third-party relays (charon-relay.dsrvlabs.dev, relay-2.prod-relay.721.land) but no .obol.dev relays Align everything with the canonical list used by Obol's own fleet (`obol-infrastructure/nodeopco/ansible/playbooks/group_vars/all.yml`): https://0.relay.obol.tech https://1.relay.obol.tech https://2.relay.obol.dev https://3.relay.obol.dev Dropped the third-party relays from .env.sample.* — operators who want them can still add them manually, but they shouldn't be part of the default Lido Simple DVT operator config.
…dev ones
Per code review feedback — keep the third-party partner relays
(dsrvlabs.dev, 721.land) in .env.sample.{mainnet,hoodi}, just append
the two new obol relays. docker-compose.yml default still ships only
the four obol relays since partners aren't part of the canonical
default; operators get them through the .env sample on first setup.
Final CHARON_P2P_RELAYS in env samples:
0.relay.obol.tech, 1.relay.obol.tech, 2.relay.obol.dev,
3.relay.obol.dev, charon-relay.dsrvlabs.dev, relay-2.prod-relay.721.land
apham0001
changed the title
OisinKyne
approved these changes
Jun 4, 2026
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
2 participants
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
Add the two new Obol-operated charon P2P relays (
2.relay.obol.dev,3.relay.obol.dev) that have already been deployed and are live in the nodeopco fleet config (obol-infrastructure/nodeopco/ansible/playbooks/group_vars/all.yml). LCDVN was missing them.Partner relays (
charon-relay.dsrvlabs.dev,relay-2.prod-relay.721.land) are preserved in.env.sample.{mainnet,hoodi}— they keep providing peer-discovery diversity for Lido Simple DVT operators.Changes
docker-compose.yml(line 98) —CHARON_P2P_RELAYSdefault now lists all 4 Obol relays:0.relay.obol.tech1.relay.obol.tech2.relay.obol.dev(new)3.relay.obol.dev(new).env.sample.mainnet+.env.sample.hoodi(line 155) — same 4 Obol relays + the 2 partner relays kept (dsrvlabs.dev + 721.land):0.relay.obol.tech, 1.relay.obol.tech, 2.relay.obol.dev, 3.relay.obol.dev, charon-relay.dsrvlabs.dev, relay-2.prod-relay.721.landTest plan
docker compose config | grep CHARON_P2P_RELAYSshows all 4 obol relays.envfrom.env.sample.mainnethas the 4 obol + 2 partner relays