Running RPC Node
RPC nodes do not directly participate in block production like consensus nodes. Instead, they are responsible for verifying transactions and facilitating communication between different nodes and between nodes and clients, promoting transaction verification and on-chain information retrieval. There are two ways to run your own RPC node:
Start it through the cess-nodeadm
Run cess-node directly.
Through cess-nodeadm
Check the latest version of cess-nodeadm Latest version of cess-nodeadm: https://github.com/CESSProject/cess-nodeadm/tags ⚠️ Replace all occurrences of
x.x.x
in the following text with the latest version number. For example, if the latest version isv0.5.5
, then replacex.x.x
with0.5.5
.Check the installed version of cess-nodeadm Enter
cess version
in the console to check if thenodeadm version
is the latest. If nodeadm is the latest version, you can skip step 3. If not, proceed to step 3 to install. If you do not see nodeadm version, it means cess-nodeadm is not installed, and you need to proceed to step 3 to install.Download and install the cess-nodeadm
Stop the RPC node service Enter the command:
cess stop chain
to stop the running RPC node service.Define script configuration parameters
Start the RPC node
Check if the RPC node is synchronizing blocks normally
Running Directly
Install the Rust environment Refer to the official Substrate tutorial
Get the latest release version of cess-node Check the latest version of cess-node
Taking v0.7.5 as the latest version, download and unzip the cess-node:
Compile cess-node
Enter the cess-node directory:
Start the RPC service
If the node is printing block synchronization logs, it means it's running successfully.
⚠️ You need to keep cess-node running at all times; it is recommended to use
screen
ortmux
commands to run cess-node in the background.
Last updated