Node Connect

To connect to an existing Gesia Node that is already running, access the running Docker container and navigate to the /root/.ethereum directory. Then, connect to the locally running Geth node using the geth attach command with the IPC file.

The reason for connecting via IPC file is because in this project, the http.api and ws.api options have been disabled to prevent the use of the admin API. This configuration enhances node security by restricting access to critical management functions exposed by the admin API. Allowing external access to these functions could pose security risks.

Once connected to the node, use the addPeer method to connect to the existing running node. Here are the connection enode addresses for each network:

Emission network

admin.addPeer("enode://6d557bc6db20965cb31f8a00272d3540902763862f3033a3f7fb323bc822c9245f31427ce7968ee092928ecc0a41b3d4cc0117ec8c4912acdcfa644d48bd025f@3.39.139.167:30403?discport=0")

Offset network

admin.addPeer("enode://78baf55de104d5cb17e2965593ea0a4c77f02d925b5fcfd5ced82202fa887a2fcdbb43dcc8a8d6fa735f2d1ea2a9b67eea7dfe45e801ee09bb47c01b25cfb5b5@43.200.218.66:30203?discport=0")

After successfully adding and confirming the return value as true, use the following command to verify if the two nodes are connected:

> admin.peers

Now, wait while the existing block information synchronizes.

Once synchronization is complete, the network is properly configured, and the nodes are connected. You can use Geth methods to inspect block information, transaction details, and more.