Mainnet/Testnet: Running Nodes using Azure 1-click Deployment
This tutorial will use our Azure 1-click Deployment image to start and create the latest Croeseid Testnet validator or full node.
CAUTION We do not recommend directly running validator on Mainnet by 1-Click deployment. Please use it with caution! Because the 1-click deployment is not running with TMKMS and your tendermint validator key is in plain text /chain/.chain-maind/config/priv_validator_key.json. You may consider running validator with tmkms on AWS nitro-enclave.
Step 1. Azure Account Creation
You will first need to create a Microsoft Azure account with a Pay-As-You-Go subscription. This will require providing your credit card information to Microsoft Azure and you may be subject to getting charged when you create a virtual machine.
Please read Microsoft Azure free trial introduction to see if you are eligible for the free-tier.
Step 2. Common Setup
Step 2-1. Search for Cronos POS Chain on Marketplace
Sign in to your Microsoft Azure account and go to Marketplace. Search for "Cronos POS Chain 1-Click Node".
Step 2-2. Create a Virtual Machine
Choose the image and click "Create" to start creating the Cronos POS Chain 1-Click Node.
1. Basic
Size
Select a recommended one or DC2s_v3
SSH public key source
Choose "existing public key"
SSH public key
Copy and paste your SSH public key
Resource group
We suggest creating a new and dedicated one so that you can easily manage resources attached to the instance
2. Disk
Follow default setting
3. Networking
Virtual network, Subnet, Public IP and NIC: "Create new" if you don't have any in that region
4. Management
Follow default setting
Boot diagnostics: default is "On". Set to "Off" if it is not required.
5. Advanced
Follow default setting
6. Tags
Create Tag if needed
7. Review + Create
Click "create" to create your instance
Step 2-3. Connect to your instance
Once the deployment is completed, you can connect to your instance via SSH.
Afterward, go to the chain directory, and you will find all the essential binaries for setting up your node:
Step 3. Running a full node
Step 3-1. Use the reconfiguration script
Now we use the reconfiguration script reconfig.sh to choose the existing networks to join.
You may also enable (Optional)STATE-SYNC. Your node will download data related to the head or near the head of the chain and verify the data. This leads to drastically shorter times for joining a network for validator. For validator, It will be amazingly fast to sync the near head of the chain and join the network.
::: warning CAUTION Blocks before state-sync trust height will NOT be queryable. If you want to run a full node or a validator with complete blockchain data; It is not suggested to use state-sync. :::
Clean up the old blockchain data (if any)
The consensus public key information could be found in /chain/.chain-maind/config/priv_validator_key.json
Backup your old /chain/.chain-maind/config/priv_validator_key.json if you created once.
The script will also ask you to fill in the moniker value which is a human-readable display name for tendermint p2p. p2p gossip will allow you to connect with more nodes (data sources).
node_id and node_key are the unique identity of your node. Save them for later use.
chain-maind is now running at the background as a systemd service.
You can check its log by the command journalctl, for example:
The consensus public key can be found by and please take a note of it for next steps:
The latest block height can be found by:
Mainnet
Testnet (testnet-croeseid-4)
Once the tendermint syncs to the latest block, the setup is done! You may move on to the next step if you want to join the network as a validator.
Step 4. Join as a validator
We suggest that you should do this process locally with chain-maind to avoid exposing your keys on a cloud server. If you haven't installed chain-maind yet, please follow Step 1. Get the Cronos POS Chain binary for testnet or Step 1. Get the Cronos POS Chain Mainnet binary for mainnet.
Last updated