Prysm BN/VC: Fix communication (#839)
This PR has 2 commits:
- Use different ports for gRPC and HTTP communication between Prysm VC
and BN
- Switch gRPC and HTTP ports to be consistent with default values.
Before this PR, we had this issue:
```
 docker inspect vc-1-geth-prysm--773bda94114946f3b501f3e293517426
[
    {
        "Id": "93713c8d7020aeb505836a11a1858e27dd9ecac19e7e7ed4814f677c30bc9c48",
        "Created": "2024-11-29T13:05:02.300408215Z",
        "Path": "/validator",
        "Args": [
            "--accept-terms-of-use=true",
            "--chain-config-file=/network-configs/config.yaml",
            "--suggested-fee-recipient=0x8943545177806ED17B9F23F0a21ee5948eCaa776",
            "--disable-monitoring=false",
            "--monitoring-host=0.0.0.0",
            "--monitoring-port=8080",
            "--graffiti=1-geth-prysm",
            "--wallet-dir=/validator-keys/prysm",
            "--wallet-password-file=/prysm-password/prysm-password.txt",
            "--beacon-rpc-provider=172.16.0.13:3500",
            "--beacon-rest-api-provider=172.16.0.13:3500",
            "--enable-beacon-rest-api"
        ],
```
```
            "--beacon-rpc-provider=172.16.0.13:3500",
            "--beacon-rest-api-provider=172.16.0.13:3500",
```
The Prysm VC tried to connect to the Prysm VC with the same port for the
beacon API and the gRPC.
Now, it is:
**VC**:
```
...
            "--beacon-rpc-provider=172.16.0.13:4000",
            "--beacon-rest-api-provider=http://172.16.0.13:3500"
...
```
BN:
```
...
 "--rpc-host=0.0.0.0",
            "--rpc-port=4000",
            "--http-host=0.0.0.0",
            "--http-cors-domain=*",
            "--http-port=3500",
...
```
---------
Signed-off-by: 
Barnabas Busa <barnabas.busa@ethereum.org>
Co-authored-by: 
Barnabas Busa <barnabas.busa@ethereum.org>
Showing
Please register or sign in to comment