# Join the Cosmos Hub Mainnet
Note: The current mainnet (
cosmoshub-4) has performed the first in-place store migration (opens new window) upgrade. That means that an upgrade proposal (opens new window) was passed to start using the v5.0.0 release of the gaia node. As a result the v4.2.1 (opens new window) version of the gaia node would panic and stop at block 6910000 (opens new window). At that point node operators installed the v5.0.5 (opens new window) version of the gaia node and then started the node again. This type of upgrade preserves the same
chain-idbut is otherwise similar to a traditional hub upgrade, meaning historical state is lost after the upgrade takes place (still accessible of course by a v4.2.1 full node).
In order to sync a gaia node from genesis the upgrade process outline above and in more detail here (opens new window) will need to take place.
To quickly sync a Cosmos Hub node it's recommended that you use the cosmos.quicksync.io (opens new window) snapshots.
This Quickstart tutorial completes the following actions:
- Ensure that you have compilation prerequisites
- Compile gaia
- Give your node a moniker and configure it
- Download compressed genesis state
- Put the
genesis.jsonfile in the correct location
Go Starts Gaia
Now wait until the chain reaches block height 6910000. It will panic and you will see a message like:
Then you should run the following commands:
Note: If your node is unable to connect to any of the seeds listed here, you can find seeds and peers in this document (opens new window) maintained by community members, and at Atlas (opens new window), which is automatically generated by crawling the network.
To save those seeds to your settings, put the comma-separated list format seeds in
~/.gaia/config/config.toml in the p2p section under seeds.
# Manual Setup of a new Node
These instructions are for setting up a brand new full node from scratch.
Make sure to have the latest gaia version installed. First, initialize the node.
Note Monikers can contain only ASCII characters. Using Unicode characters is not supported and renders your node unreachable.
By default, the
init command creates your
~/.gaia directory with subfolders
config directory, the most important files for configuration are
You can edit the
moniker in the
For optimized node performance, edit the
~/.gaia/config/app.toml file to enable the anti-spam mechanism and reject incoming transactions with less than the minimum gas prices:
Your full node has been initialized!
# Genesis & Seeds
# Copy the Genesis File
Fetch the mainnet's
genesis.json file into
gaiad's config directory.
If you want to connect to the public testnet instead, click here
To verify the correctness of the configuration run:
# Add Seed Nodes
Your node needs to know how to find peers. You'll need to add healthy seed nodes to
launch (opens new window) repo contains links to some seed nodes.
If those seeds aren't working, you can find more seeds and persistent peers on a Cosmos Hub explorer (a list can be found on the launch page (opens new window)).
# A Note on Gas and Fees
On Cosmos Hub mainnet, the accepted denom is
1atom = 1.000.000uatom
Transactions on the Cosmos Hub network need to include a transaction fee in order to be processed. This fee pays for the gas required to run the transaction. The formula is the following:
gas is dependent on the transaction. Different transaction require different amount of
gas amount for a transaction is calculated as it is being processed, but there is a way to estimate it beforehand by using the
auto value for the
gas flag. Of course, this only gives an estimate. You can adjust this estimate with the flag
1.0) if you want to be sure you provide enough
gas for the transaction.
gasPrice is the price of each unit of
gas. Each validator sets a
min-gas-price value, and will only include transactions that have a
gasPrice greater than their
fees are the product of
gasPrice. As a user, you have to input 2 out of 3. The higher the
fees, the higher the chance that your transaction will get included in a block.
For mainnet, the recommended
Your full-node keeps unconfirmed transactions in its mempool. In order to protect it from spam, it is better to set a
minimum-gas-prices that the transaction must meet in order to be accepted in your node's mempool. This parameter can be set in the following file
The initial recommended
0.0025uatom, but you might want to change it later.
# Pruning of State
There are four strategies for pruning state. These strategies apply only to state and do not apply to block storage.
To set pruning, adjust the
pruning parameter in the
The following pruning state settings are available:
everything: Prune all saved states other than the current state.
nothing: Save all states and delete nothing.
default: Save the last 100 states and the state of every 10,000th block.
custom: Specify pruning settings with the
By default, every node is in
default mode which is the recommended setting for most environments.
If you would like to change your nodes pruning strategy then you must do so when the node is initialized. Passing a flag when starting
gaia will always override settings in the
app.toml file, if you would like to change your node to the
everything mode then you can pass the
---pruning everything flag when you call
Note: When you are pruning state you will not be able to query the heights that are not in your store.
# Run a Full Node
Start the full node with this command:
Check that everything is running smoothly:
View the status of the network with the Cosmos Explorer (opens new window).
# Enable the REST API
By default, the REST API is disabled. To enable the REST API, edit the
~/.gaia/config/app.toml file, and set
true in the
Optionally, you can activate swagger by setting
true or change the port of the REST API in the parameter
After restarting your application, you can access the REST API on
# GRPC Configuration
By default, gRPC is enabled on port
9090. In the
~/.gaia/config/app.toml file, you can make changes in the gRPC section. To disable the gRPC endpoint, set
false. To change the port, use the
To be best prepared for eventual upgrades, it is recommended to setup Cosmovisor (opens new window), a small process manager, which can swap in new
gaiad binaries. Read more about setting this up here.
# Background Process
To run the node in a background process with automatic restarts, you can use a service manager like
systemd. To set this up run the following:
If you're using Cosmovisor you want to add
LimitNOFILE line and replace
$(which gaiad) with
Then setup the daemon
We can then start the process and confirm that it is running
# Export State
Gaia can dump the entire application state into a JSON file. This application state dump is useful for manual analysis and can also be used as the genesis file of a new network.
Export state with:
You can also export state from a particular height (at the end of processing the block of that height):
If you plan to start a new network from the exported state, export with the
# Verify Mainnet
Help to prevent a catastrophe by running invariants on each block on your full node. In essence, by running invariants you ensure that the state of mainnet is the correct expected state. One vital invariant check is that no atoms are being created or destroyed outside of expected protocol, however there are many other invariant checks each unique to their respective module. Because invariant checks are computationally expensive, they are not enabled by default. To run a node with these checks start your node with the assert-invariants-blockly flag:
If an invariant is broken on your node, your node will panic and prompt you to send a transaction which will halt mainnet. For example the provided message may look like:
When submitting a invariant-broken transaction, transaction fee tokens are not deducted as the blockchain will halt (invariant-broken transactions are free transactions).