Create staker network

[pablomendezroyo]

Create staker network for staker pkgs engine communications: staker_network

• It will have an initial migration where it will connect selected consensus and execution clients from every network to the staker_network as well as writing the corresponding compose configuration in the docker-compose.yml file. It will also add a fullnode alias to the execution client, to be used by the consensus client in the engine communication
• It will take the same approach on every user selection in the stakers
• Furthermore, it will attempt to disconnect any other client from the stakers and remove the corresponding configuration from the compose file for reliability.

Benefits:

• More flexibility when adding new execution/consensus client. There will not be needed a release of every client allowing this new client, but just a core release
• Stop from using global envs: this will have an impact of stopping from restarting packages that use global envs to realize whenever its used a specific execution/consensus client. Instead, it will be used a single unique domain.
• Clients pkgs entrypoints simplification

Next steps

• Test
• Use single JWT per network
• Use fullnode domain in consensus clients

[github-actions[bot]]

🚀 Deployed on https://667557e2d230f55b4e0107a4--objective-borg-9eeae5.netlify.app

[github-actions[bot]]

Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 33ca2054ee6df205df3a70a255f4cb69e34a9eb8

This is a development version and should only be installed for testing purposes.

(by dappnodebot/build-action)