Last updated
Last updated
Full nodes are general instructions to join the Gluon mainnet after network genesis.
For streamline chain upgrades and minimize downtime, you may want to set up to manage your node.
Follow
To automate on-chain upgrades, set the following options.
If you are using a recent version of Cosmovisor, then the default configuration is that a state backup will be created before upgrades are applied. This can be turned off using .
Alerting and monitoring are desirable as well - you are encouraged to explore solutions and find one that works for your setup. Prometheus is available out-of-the-box, and there are a variety of open-source tools.
The following hardware minimum requirements are recommended for running the validator node:
Memory: 32 GB RAM (or equivalent swap file set up)
CPU: 8 cores (4 physical core) x86_64
Disk: 1 TB SSD Storage (See below for details)
Bandwidth: 1 Gbps for Download/1 Gbps for Upload
An archival node (pruning = "nothing") should have at least 64GB of dedicated memory
An archival node (pruning = "nothing") grows at a rate of ~100 GB per month Current total disk usage is 6TB, so a larger disk would be necessary.
A full pruning node (pruning = "everything") grows at a rate of ~5 GB per month
A default pruning node (pruning = "default") grows at a rate of ~25 GB per month
Set chain-id & moniker. moniker is just a name for your node.
This will generate the following files in ~/.gluon/config/
genesis.json
node_key.json
priv_validator_key.json
For mainnet:
For testnet:
Persistent peers will be required to tell your node where to connect to other nodes and join the network. To retrieve the peers for the chosen chain-id:
For RPC nodes and Validator nodes, we recommend setting the following minimum-gas-prices. As we are a permissionless wasm chain, this setting will help protect against contract spam and potential wasm contract attack vectors.
In $HOME/.gluon/config/app.toml, set minimum gas prices:
If necessary, Edit config files ~/.gluon/config/app.toml
Enable defines if the API server should be enabled.
EnableUnsafeCORS defines if CORS should be enabled (unsafe - use it at your own risk).
If you want to query the historical state — for example, you might want to know the balance of a wallet at a given height in the past — you should run an archive node with pruning = "nothing" in app.toml. Note that this configuration is resource-intensive and will require significant storage:
If you want to save on storage requirements, consider using pruning = "everything" in app.toml to prune everything.
Either create a new key pair or restore an existing wallet for your validator:
You will require some GLU tokens to bond to your validator. To be in the active set you will need to have enough tokens.
Follow the instructions to set up Cosmovisor and start the node.
Using cosmovisor is completely optional. If you choose not to use cosmovisor, you will need to be sure to attend network upgrades to ensure your validator does not have downtime and get jailed.
If you are not using Cosmovisor, run the following:
After starting the gluond daemon, the chain will begin to sync to the network. The time to sync to the network will vary depending on your setup and the current size of the blockchain but could take a very long time. To query the status of your node:
This command returning true means that your node is still catching up. Otherwise, your node has caught up to the network's current block and you are safe to proceed to upgrade to a validator node.
If you want to shorten the time to catch up to the latest block, consider using snapshots from other nodes.
If you want to catch up from 0 height, you have to upgrade gluond at each upgrade heights.
The tutorial is done on Ubuntu 22.04 (LTS). Follow