Skip to content

Conversation

@maoueh
Copy link
Contributor

@maoueh maoueh commented Dec 2, 2025

This change, relatively simple and backward compatible, enables syncing an external execution client from the host itself instead of relying on running within Docker. We tested it and to succesfully sync with the inner el peer, one further change is needed which is to expose the P2P address to the public interface (instead of only within the host), PR incoming for this.

This change, relatively simple and backward compatible, enables syncing an external execution client from the host itself instead of relying on running within Docker. We tested it and to succesfully sync with the inner el peer, one further change is needed which is to expose the P2P address to the public interface (instead of only within the host), PR incoming for this.
Copilot AI review requested due to automatic review settings December 2, 2025 16:28
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for using a secondary execution layer (EL) client on the host machine instead of requiring it to run within Docker. The implementation changes the secondaryEL field from a port number to a string that accepts either a port or a full address, maintaining backward compatibility.

Key Changes:

  • Modified secondaryEL field from uint64 (port only) to string (port or address)
  • Added regex-based logic to distinguish between port-only and full address inputs
  • Updated documentation to explain both usage patterns (port vs full address)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

1 participant