RPC
How to deploy a full-node RPC
A Remote Procedure Call (RPC) allows programs that run on one device, or network, to execute functions and procedures on another. The primary purpose of an RPC is to enable communication and cooperation between distributed components of a system, allowing developers to create applications that leverage the functionality of remote devices or services. To enable a software application to engage with the XDC blockchain, whether it involves accessing blockchain data, smart contract executions, interacting with the network, or executing transactions, it needs to establish a connection with an XDC node. These RPC nodes are deployed on the network, however, they do not participate in validation or consensus.
JSON-RPC is a streamlined and efficient remote procedure call (RPC) protocol that operates without maintaining a state. It outlines various data structures and their corresponding processing rules. This protocol remains adaptable to different transport mechanisms, such as within the same process, over sockets, over HTTP, or across various message-passing environments.
How to deploy RPC
Requirements and prerequisites:
A server or cloud instance with at least 16 GB of RAM and 512 GB of storage.
Ubuntu 22.04 LTS or higher operating system (Recommended)
Basic knowledge of the Linux command line.
Step 1: Setting up the full node with docker Clone repository
Enter XinFin-Node directory
Install docker & docker-compose
Update the .env file with details:
Create a .env file by using the sample — .env.example
Enter either your company or product name in the INSTANCE_NAME field.
Enter your email address in the CONTACT_DETAILS field.
Start your Node
To stop the node, or if you encounter, any issues use
Attach XDC Console:
You can check the status of your full node on the stats page at
If you want your full node to sync faster, you can download the latest Mainet snapshot from:
Follow the below steps to unpack and restore the snapshot. This will synchronize the node faster since there will very less blocks to catchup on:
sudo docker-compose -f docker-compose.yml down
tar -xvzf xdcchain.tar
rm -rf xdcchain/XDC
mv XDC xdcchain/XDC
sudo docker-compose -f docker-compose.yml up -d
After downloading the snapshot, monitor your node on the stats page mentioned above. Once your node is fully synced, you can start using the dedicated RPC.
To access RPC on your newly configured node use the below format:
http://x.x.x.x:8989, where x.x.x.x is your public or private IP address for the node.
Similarly you can access the webSockets on your newly configured node by using the below sample URL:
wss://x.x.x.x:8888, where x.x.x.x is your public or private IP address for the node.
XDC and 0x prefix
The XDC Network uses an XDC prefix instead of the 0x prefix used by some EVM-compatible networks, however, 0x can still be used when interacting with the network by using an XDC and 0x compatible RPC. The 0x prefix is not enabled by default and needs to be enabled manually by editing and updating startnode.sh file and passing a flag.
To enable the 0x prefix RPC Endpoint, you can add the flag “— enable-0x-prefix” to your “startnode.sh” script. This will allow the RPC Endpoint to recognize and process 0x-prefixed
Last updated