Running RPC Node
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
Check the latest version of cess-nodeadm
Latest version of cess-nodeadm:
β οΈ Replace all occurrences of x.x.x in the following text with the latest version number. For example, if the latest version is v0.6.1, then replace x.x.x with 0.6.1.
Check the installed version of cess-nodeadm
Enter cess version in the console to check if the nodeadm 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
The archive mode saves all blocks, which is suitable for full node operation, otherwise, you can set the number of blocks to be saved
Start the RPC node
Check if the RPC node is synchronizing blocks normally
Environment Setup Requirements
OS required: Ubuntu 20+
Rust install:
Dependencies install:
ProtoBuf install (run as root):
You can get the latest version using one of the following methods:
Method 1: Download and unzip the release (e.g., cess-0.7.9-venus as example):
Method 2: Clone the repository with the latest tag:
Compile cess-node
Enter the cess-node directory:
β οΈ Note: The compilation may take approximately 25 minutes on an 8-core machine.
Start the RPC service
Use the -h flag to view more command options.
β οΈ Special note for --wasm-runtime-overrides: Due to the online upgrade of SGX in the current testnet, it is necessary to specify special wasm files for overriding. For example, if the spec_100.wasm file is located at /opt/wasm/, the parameter should be filled in as --wasm-runtime-overrides /opt/wasm. You only need to specify the directory path, not the file path. Currently, we have placed the spec_100.wasm file in the /scripts/wasm_overrides/testnet/ path within the cess repository.
If the node is printing block synchronization logs, it means it's running successfully.
β οΈ It is recommended to use systemd, screen or tmux commands to run cess-node(RPC) if you want to keep cess-node running.
Environment Setup Requirements
Running Command
Make sure that port 30336 and 9944 are not occupied by other processes.
Execute docker run -it --rm --entrypoint /opt/cess/cess-node cesslab/cess-chain:testnet --help to get more information about the command options.
Check if the RPC node is synchronizing blocks normally
The rpc node log is down below and start to synchronize blocks.
Get the latest release version of cess-node