Update consensus node CHAIN_ID to 298

[Kalina-Todorova]

Description

As noted in the https://github.com/hashgraph/hedera-json-rpc-relay/ README:
The network chain id. Local and previewnet envs should use 0x12a (298). Previewnet, Testnet and Mainnet should use 0x129 (297), 0x128 (296) and 0x127 (295) respectively
Let's update the CHAIN_ID to be the correct one for local environment.

Steps to reproduce

When running the local node.

Additional context

No response

Hedera network

other

Version

v1.2.0

Operating system

No response

[mshakeg]

@Kalina-Todorova is this issue related to this issue I came across in the example projects.

[georgi-l95]

Probably yes, local node was configured to work with testnet - 0x128 (296) , while relay is configured to work with 0x12a (298) .This should be fixed now.

[mshakeg]

@georgi-l95 thanks for the reply. I see, would you happen to know when's the next @hashgraph/hedera-local release and if there's a temp fix/workaround for devs until then?

[georgi-l95]

Not sure about next release, but you can start the relay locally and after that start the hedera-local (this way the relay container won't start). Just make sure their chain id are the same. Either testnet or local. Checkout how to start it in the relay repo.

[mshakeg]

@georgi-l95 I started the relay up and then the hedera-local node, however there seems to be a health check on the relay container which basically shuts down the entire docker service if it's not healthy.

Starting the docker containers...
Stopping the network...
Stopping the docker containers...
Cleaning the volumes and temp files...
Waiting for the containers at 127.0.0.1:5600, retrying in 20 seconds...
Error: connect ECONNREFUSED 127.0.0.1:5600
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 5600
}

Edit:
Managed to get it working using the testnet CHAIN_ID in the relay .env