Validator Node
Last updated
Last updated
Validator nodes are critical to the Sonic chain, responsible for validating transactions and creating new blocks in accordance with the . These nodes ensure the integrity and security of the network by verifying data, participating in block creation, and maintaining the chain’s state.
Unlike , validator nodes focus on real-time operations rather than storing extensive historical data or responding to general API requests.
To run a validator node on the Sonic mainnet or Blaze testnet, follow the steps below.
Minimum self-stake amount: 500,000 S
Maximum validator size: 15x self-stake
Rewards: ~6% APR initially, plus 15% of delegators' rewards and network fees
You can run your validator node on dedicated hardware (bare metal) or use a cloud provider. We recommend choosing one of the established providers, such as Google GCP or Amazon AWS.
At least 4 vCPUs and 32 GB of RAM
At least 1 Gbps redundant backbone connectivity for stable and uninterrupted network traffic
At least 1 TB of local SSD/NVMe storage. Remote block devices (e.g., AWS EBS) typically do not provide the required latency and random access performance. Google GCP N2D instances with local SSD or AWS i3en.xlarge with instance storage are good options.
Ubuntu LTS Server (64-bit) or a similar Linux distribution is recommended.
1 TB of local SSD/NVMe is sufficient for a validator database.
A Sonic node requires both TCP and UDP network traffic allowed on port 5050 by default. You can use --port <port> to customize this if needed.
You need the essential build tools and the latest Go compiler, version 1.22 or newer, to build the Sonic client and its bundled tools. Example (Ubuntu/Debian):
Install Go language compiler (Ubuntu/Debian):
Check the latest Sonic release and adjust commands if necessary:
You can confirm the Sonic release by running:
Optionally, copy the binaries to a system-wide location:
Use sonictool to prime the state database. Adjust GOMEMLIMIT and --cache according to your available RAM size. For the most common cases, use 12GiB as --cache and ~90% of RAM as GOMEMLIMIT.
After processing, you should see a confirmation of a successfully imported state.
Now that your database is primed, start the node to synchronize it with the network. Ensure your firewall is configured correctly.
The Sonic node will connect to the network and advance its state by processing new blocks. Once fully synchronized, the "age" of new blocks should be only a few seconds.
Your Sonic node is now synchronizing. Next, create a wallet to identify and control your validator account. This wallet must hold the minimum amount you are going to use as the self-stake (500,000 S).
We recommend creating the wallet securely (e.g. a hardware wallet). If you choose to create it locally using sonictool:
Important: Keep your wallet and keys secure. Never share them.
A Sonic validator node signs consensus messages. Your node needs a validator signing key to participate. Create it on the server:
Follow the prompts and set a secure password. Note the public key (starts with 0xc00). This key will be used during registration.
Important: Back up your signing key. Although it cannot move funds, misuse could lead to penalties.
The network must recognize your validator key. Register by invoking the SFC (Staking and Consensus) contract:
The contract is validated and you can interact with it using SonicScan and a connected Web3 wallet. The control validator account can be imported into your Web3 wallet either using the generated JSON key store or as your hardware wallet. With the account open, you can sign the createValidator transaction call specifying the amount of stake and the public key obtained in the previous step.
Stop the currently running node:
Wait for it to gracefully shut down. Never force-terminate it, as it could corrupt the database. Restart your node in validator mode, providing the validator ID, public key, and password file:
Your validator node will now participate in consensus and produce blocks.
Create a config file in JSON format that contains the following parameters (you can also leave parameters empty):
Now you need to insert the JSON URL into the STI contract.
Hit Contract -> Write Contract.
Find the function updateInfo and paste the JSON URL.
Connect using your validator account Web3 wallet (the one you used to register).
Sign and execute the update.
Congratulations! You are now running a Sonic validator node.
To participate in the Sonic network, you need a valid state database. The fastest way is to use a genesis file from the official repository. Download the . For the mainnet, for example:
SFC Contract Address:
Call createValidator with your validator public key and at least the minimum required stake (500,000 S). Sign this transaction with your validator wallet. After confirmation, query your validator ID using the getValidatorID function. The easiest way would be to open the and navigate to the SFC address.
Host it somewhere so it is publicly accessible, such as in . Make sure anybody can download the JSON file using a browser and that the hosting site supports HTTPS. A 100x100 logo size is sufficient.
Go to and open the .
Validator/Name Logo
Community and Help
Monitoring and Health
If your node goes offline, you stop earning rewards. Extended downtime (e.g. more than 5 days) may result in suspension, requiring you to withdraw and start over. Regular monitoring, maintenance, and backups are essential.
You can set a validator name and logo on the explorer. Check for instructions.
The STI contract on Sonic:
Join , follow updates, and use your stake to participate in network governance. If you have issues, the community can provide guidance.
