Starting a Full Node

How to Run an Onomy Full Node

Minimum system requirements:
  • Any modern Linux distribution (RHEL 8 or Fedora 36 are preferred)
  • A quad-core CPU
  • 16 GB of RAM
  • 320 GB of storage
Make sure you have gone through Installation Steps prior to setting up a node.
There are a couple of ways to initialize and start a full node
  1. 2.
    Initialize and start a full node manually

Initialize and start a full node using scripts

  1. 1.
    To start the Onomy full node, download scripts from the GitHub.
mkdir $HOME/.onomy/scripts
cd $HOME/.onomy/scripts
2. Add executable permissions to the scripts using chmod +x *
3. Download genesis file
4. Run script to initiate a new full node
This script will ask you for several details
  • Node Name [Text]: A name for your full node
  • Seed IPs [Comma separated list of IPs]: IP Addresses of seed nodes, There are a couple of IPs pre-configured, If you want to point your node to custom Seed node, you can do that here
  • Your IP Address [IP Address]
After the script is done, you will find node-id in the output. Make sure to take a note of the node id as you might need it afterwards. If you forgot to save your node id, you can find it using
onomyd tendermint show-node-id
4. [Optional] you can allow CORS using the script
5. You can start and stop the node using and When you first start the node, give it enough time to sync with the blockchain

Initialize and start a full node manually

  1. 1.
    Initialize onomy node and config files
onomyd init <node name> --chain-id onomy-mainnet-1
  1. 2.
    Copy Genesis file from onomy repo
If Onomy Github repository was downloaded in previous step, copy genesis file from the repo
cp onomy/genesis/genesis-mainnet-1.json $HOME/.onomy/config/genesis.json
Otherwise, download genesis file using wget
cp genesis-mainnet-1.json $HOME/.onomy/config/genesis.json
  1. 3.
    Change config to add various details
crudini --set $HOME/.onomy/config/config.toml p2p addr_book_strict false
crudini --set $ HOME/.onomy/config/config.toml p2p external_address "\"tcp://<ip-address>:26656\""
crudini --set $ HOME/.onomy/config/config.toml p2p seeds "\”[email protected]:26656, [email protected]:26656\”"
crudini --set $ HOME/.onomy/config/config.toml rpc laddr "\"tcp://\""
crudini --set $HOME/.onomy/config/app.toml grpc enable true
crudini --set $HOME/.onomy/config/app.toml grpc address "\”\”"
crudini --set $HOME/.onomy/config/app.toml api enable true
crudini --set $HOME/.onomy/config/app.toml api swagger true
  1. 4.
    Setup state-sync (Optional)
We can setup state-sync to quickly sync up the node
These are the IP addresses for state sync nodes:,
Open one RPC endpoint of one of the state-sync nodes to get the details of latest block:
  • Get latest block height from result.block.header.height parameter and latest block hast from result.block_id.hash parameter
  • Change the following parameters in config.toml file
crudini --set $ONOMY_NODE_CONFIG statesync enable true
crudini --set $ONOMY_NODE_CONFIG statesync rpc_servers "\" [email protected]:26657,[email protected]:26657\""
crudini --set $ONOMY_NODE_CONFIG statesync trust_height <block height from previous step>
crudini --set $ONOMY_NODE_CONFIG statesync trust_hash "\" <block hash from previous step> \""
crudini --set $ONOMY_NODE_CONFIG statesync discovery_time "\"60s\""
crudini --set $ONOMY_NODE_CONFIG statesync chunk_request_timeout "\"60s\""
crudini --set $ONOMY_NODE_CONFIG statesync chunk_fetchers "\"10\""
  1. 5.
    Start the node
  • Increase open file limit to more than 65535
ulimit –n 65536
  • Start onomyd
onomyd start
  • If you are using cosmovisor then start cosmovisor
cosmovisor start

Check the status of the Onomy chain

You should be good to go! You can check the status of the Onomy chain by running:
curl http://localhost:26657/status
Your node is fully synced when catching_up is false.
You can also open the http://localhost:26657 in your browser and check available end-points