Skip to content

feat: add 2.relay.obol.dev + 3.relay.obol.dev to charon p2p relays#477

Merged
apham0001 merged 1 commit into
mainfrom
feat/add-relay-2-3-dev
Jun 4, 2026
Merged

feat: add 2.relay.obol.dev + 3.relay.obol.dev to charon p2p relays#477
apham0001 merged 1 commit into
mainfrom
feat/add-relay-2-3-dev

Conversation

@apham0001
Copy link
Copy Markdown
Contributor

Summary

Obol stood up two new charon P2P relays (2.relay.obol.dev and 3.relay.obol.dev). They've already been added to the nodeopco fleet config (see obol-infrastructure nodeopco/ansible/playbooks/group_vars/all.yml) but were missing from the CDVN docker-compose default — every operator running the stock stack only connected to 0+1.relay.obol.tech.

Changes

docker-compose.yml:

  • CHARON_P2P_RELAYS default now lists all 4 relays:
    • 0.relay.obol.tech
    • 1.relay.obol.tech
    • 2.relay.obol.dev (new)
    • 3.relay.obol.dev (new)

.env.sample.mainnet/hoodi untouched — the #CHARON_P2P_RELAYS= line there is for users who want to override the defaults with a custom list, not the default itself.

Test plan

  • docker compose config | grep CHARON_P2P_RELAYS shows all 4 relays
  • Restart charon container, confirm peer discovery picks up new relays in logs

Obol stood up two new charon P2P relays (2.relay.obol.dev and
3.relay.obol.dev) — they've already been added to the nodeopco fleet
config but were missing from the CDVN docker-compose default, which
means every operator using the default stack was only connecting to
0+1.relay.obol.tech.

Update the CHARON_P2P_RELAYS default to include all four relays so new
operators get the full peer-discovery network out of the box.
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 4, 2026

@apham0001 apham0001 merged commit bbb2ef1 into main Jun 4, 2026
4 checks passed
@apham0001 apham0001 deleted the feat/add-relay-2-3-dev branch June 4, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants