Full Node Synchronization

Introduction

The Full Node Synchronization service is now available for standalone purchase. Users who subscribes to Tier 2 or higher will receive a free quota (the number of full nodes allowed for connection) based on your plan tier.

The full-node synchronization service enables low-latency synchronization for Ethereum clients, leveraging high-performance networks. Different from subscribing to block data streams, Ethereum client can directly establish P2P connections with Relay in nearby areas, which synchronizes the latest blocks to the Ethereum clients through P2P network. Users can obtain the latest block events and world state in the first time.

Price & Free quota

The Full Node Synchronization service is available for separate purchase, and the price of a single enode is detailed in the table below. Users who subscribes to Tier 2 or higher will receive a free quota (the number of full nodes allowed for connection) based on your plan tier.

Standalone Purchase

Service Duration	Discount	Price
1 month	100%	$500(1 * $500)
3 months	95%	$1425(3 * $475)
6 months	90%	$2700(6 * $450)
9 months	85%	$3825(9 * $425)
12 months	80%	$4800(12 * $400)

Free Quota of Subscription Plan

	Tier 4	Tier 3	Tier 2	Tier 1	Tier 0
Number of full nodes allowed to connect	-	-	2	5	30

Relay IP

Region	Availability Zone(AWS)	Relay Address
Frankfurt	euc1-az2	35.157.64.49:50051
Tokyo	apne1-az4	54.249.93.63:50051
Ireland	euw1-az1	3.248.65.151:50051
Virginia	use1-az4	52.205.173.134:50051

Instruction

Step 1: Add Enode

Add Enode for Free

1. Go to https://www.blockrazor.io, click [Register] in the upper right corner to complete the registration

2. Log in to the Portal, go to [Pricing], select Tier 2 or above, and click [Get Started]

1. Confirm the subscription duration and payment method and complete the payment

2. Go to [Service] - [Full Node Sync], click [Add Enode]

1. Select the region where Relay is located (it is recommended to select the region closest to the geographical location of your Geth node), enter the Enode of the Ethereum client that needs to be connected, and click [Confirm] to complete the addition.

1. Return to the Enode list and click [Copy Relay Enode]

Purchasing Enode separately

1. Go to https://www.blockrazor.io, click [Register] in the upper right corner to complete the registration

2. Go to [Service] - [Full Node Sync], click [Add Enode]

1. Select the region where Relay is located (it is recommended to select the region closest to the geographical location of your Geth node), enter the Enode of the Ethereum client that needs to be connected, and click [Confirm]

1. Confirm the service duration and payment method and complete the payment

2. Return to the Enode list and click [Copy Relay Enode](Note: the enode is created only when the payment is completed)

Step 2: Open ports to allow relay access

If your Ethereum client is deployed on AWS or other cloud services, you should additionally configure inbound rules for the security group.

1. Access your own Ethereum client's server and execute commands to set up the firewall to allow Relay access.

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="52.205.173.134" port port="30311" protocol="tcp" accept'

• "source address" is the IP of Relay which can be acquired from Relay IP

• The port for the Ethereum client to allow Relay access is generally set as the default, which is 30311. You can modify this based on your own node configuration.

1. Reload the firewall configuration to make the changes take effect.

sudo firewall-cmd --reload

Step 3: Check the connection status（Enable the admin namespace in the Geth node as an example）

1. Wait for 10 minutes, access the Geth node, execute the curl command to check the connection status

curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"admin_peers","params":[],"id":1}' http://localhost:8545

1. In the returned data, query the Relay Enode address (which can be copied from the Portal). If the address is found, it proves that the connection is successful.

[
    {
        "enode": "enode://9ddacbcca0dc1d1b112d470552acc795fce5c3e9f50983fcd5cee7b47289914295acaef3163bea819bcc967461978425def13595deb7de4063295c40e593f320@52.205.173.134:53754",
        "id": "8be29a75ac2cf81e3aa37ccc119630a9dfc43c88d7b5200398a466f5ef9097c4",
        "name": "Geth/v1.4.5/linux-amd64/go1.21.7",
        "caps": [
            "eth/68"
        ],
        "network": {
            "localAddress": "127.0.0.1:30311",
            "remoteAddress": "52.205.173.134:53754",
            "inbound": true,
            "trusted": false,
            "static": false
        },
        "protocols": {
            "eth": {
                "version": 68
            }
        }
    }
]

If the connection status is found to be abnormal after inquiry, it may be due to network communication problems between nodes. Please go to Discord to contact us.