Not able to connect two nodes after separating the testnet.sh into different files ? (Like bootnode.sh , gethnode.sh , beaconnode.sh , validator.sh)

[cryptonix21]

Hi @rzmahmood !
Hope you are doing well,

I split the 'testnet. sh' files into separate files to monitor two nodes in different terminals. However, when I ran these nodes in separate terminals, they both created two blockchains with the same chain ID. When I tried transferring the native balance, I noticed that the balances were displaying different values on two different RPC URLs, even though they shared the same chain ID. How to check nodes are connected with each other?

[rzmahmood]

You can check if nodes are attached to each other by following the geth attach mechanism to open the JS console shown in the README. This will allow you to inspect the peers of each nodes.

To allow the two different blockchains to discover each other, you need to make sure the Execution client discovery mechanism and consensus client discovery mechanism are being facilitated.

For the execution client, make sure that both execution clients (geth) on both files are being started with the --bootnodes flag pointing to the same bootnode.

For the consensus client (prysm), make sure that the second prysm node is being run with the --bootstrap-node pointing to the first node.

Both of the above are demonstrated in testnet.sh

[cryptonix21]

Hi @rzmahmood!
Hope you are doing well,
I have tried way above you mentioned but still facing the same issue and I am sharing my geth node and beacon node files, Please check the files once.
2_beacon_node.txt
1_beacon_node.txt
2_geth_node.txt
1_geth_node.txt