Manage your nodes

Add a node to a network

Once you have joined a public network or deployed a consortium network, you can add more nodes to the network.

For consortium networks, you can add a node to run in cross cloud, cross region, and hybrid networks starting from the Enterprise subscription plan.

For public networks, you can add an elastic or a dedicated node.

To add a node:

1. Select the project with the network.
2. Select the network.
3. Click Add node.

The status will change from Pending to Running once deployed.

View node status

You can view the node and network status in the Status column of your nodes list.

Node statuses

📘

In the unlikely case that a node enters a failed state or an error state, there is no action required on your part as the Chainstack team will be immediately alerted and resolve the issue.

View node access and credentials

To view the access information:

1. Click your project.
2. Click your network.
3. Click the node name.

This will give you the access and credentials to your nodes.

Public chain nodes

Examples of your HTTPS node connection endpoints:

https://nd-123-456-789.p2pify.com/3c6e0b8a9c15224a8228b9a98ca1531d

https://user-name:[email protected]

Examples of your WSS node connection endpoints:

wss://ws-nd-123-456-789.p2pify.com/3c6e0b8a9c15224a8228b9a98ca1531d

wss://user-name:[email protected]

Consortium nodes

If you are an invited member of a consortium project, you will be able to see the basic access information of other nodes in the project.

Quorum has the node access set up in the same way as public chain nodes.

View node requests metrics

You can view the data on requests made to your public chain project node.

To view the requests data:

1. Click your project.
2. Click your network.
3. Click the node name.

This will show you the data on the requests made to your node:

• Requests made — a chart of the total requests over HTTP and WebSocket for the selected period.
• Method calls — a breakdown of the method calls to the node over the selected period. Only available for HTTP requests.
• Response codes — a breakdown of the HTTP response status codes over the selected period. Only available for HTTP requests.

Switch the period

To switch the period of the displayed requests data:

1. Navigate to the Metrics section.
2. On your right, select the period.

Download the aggregate data

To download the aggregate requests data:

1. In the Requests made section, click the hamburger button.
2. Click the format to download the aggregate data.

Check dedicated nodes resources allocation

You can view the resources dynamically allocated to each of your dedicated nodes.

To view the resources allocated to your nodes:

1. Click your project.
2. Click your network.
3. Click the node name.
4. Under Resources, hover over Dynamic.

Understand node resources allocation

Public chains resources

📘

Ancient storage

The ancient storage is for the Geth freezer database to separately keep the ledger data older than three epochs. See also an Ethereum blog post for the detailed freezer. You are not charged for the ancient storage.

Stop or start a node

You can stop and start your deployed nodes.

A stopped node in Chainstack-provided hosting retains its state and does not incur metered compute costs but does incur storage costs.

A stopped node in private hosting does not incur maintenance costs.

A stopped node does not sync. When you start a stopped node, the node will start syncing again and will take some time to fully sync.

To stop or start a node:

1. Click your project.
2. Click a network in the project.
3. Select the node to stop or start. Click Stop or Start.

In a consortium project, stopping the first deployed peer node will stop the entire network, including the service nodes.

Delete a node

🚧

To be able to delete a project or a network, you must first delete all nodes associated with the network.

To delete a node:

1. Click your project.
2. Click a network in the project.
3. Select a peer node to delete. Click Edit > Delete.

When deleting nodes in a consortium project:

• You can only delete the first deployed peer node after deleting all other peer nodes in the network.
• Deleting the first deployed peer node will delete the entire network, including the service nodes.