The resulting folder changechain-<VERSION>-linux contains the binaries.
2. Start the Node
MacOS
Mainnet:
Testnet:
Linux
Mainnet:
Testnet:
Networking
To successfully run the Change Chain node and participate in the network, ensure that your node can accept connections on network port 9651.
Running on a Cloud Provider
If you're running your node on a cloud service like AWS, Azure, or Google Cloud:
Configure your cloud instance's firewall settings to allow inbound and outbound traffic on port 9651.
Ensure your security groups and network access control lists (ACLs) permit traffic on this port.
Running on a Home Connection
If you're running your node from home:
Set up port forwarding on your router to forward external traffic on port 9651 to your machine's local IP address.
Check your computer's firewall settings to allow traffic on port 9651.
Note: To make API calls to your node from other machines, include the argument --http-host=0.0.0.0 when starting the node:
Bootstrapping
When starting your node for the first time, it needs to catch up with the latest network state, a process known as bootstrapping. This may take several hours depending on your internet connection and hardware performance.
Check Bootstrapping Progress
You can check if your node has finished bootstrapping a particular chain by using the info.isBootstrapped API method.
Example Command
Replace "chain": "C" with "X" or "P" to check the status of the other chains.
Interpreting the Response
If the response returns true, the chain has finished bootstrapping.
If the response returns false, the chain is still bootstrapping.
RPC Endpoints
Once your node has bootstrapped, the following RPC endpoints become available:
Change Chain: http://localhost:9651/ext/bc/C
If accessing remotely, replace localhost with your node's public IP address.
For detailed API documentation, refer to the Change Chain API Reference.