::: tip See the genesis repo for information on the mainnet, including the correct version of the Xar-SDK to use and details about the genesis file. :::
::: warning You need to install xar before you go further :::
These instructions are for setting up a brand new full node from scratch.
First, initialize the node and create the necessary config files:
xard init <your_custom_moniker>
::: warning Note Monikers can contain only ASCII characters. Using Unicode characters will render your node unreachable. :::
You can edit this
moniker later, in the
# A custom human readable name for this node moniker = "<your_custom_moniker>"
You can edit the
~/.xard/config/xard.toml file in order to enable the anti spam mechanism and reject incoming transactions with less than the minimum gas prices:
# This is a TOML config file. # For more information, see https://github.com/toml-lang/toml ##### main base config options ##### # The minimum gas prices a validator is willing to accept for processing a # transaction. A transaction's fees must meet the minimum of any denomination # specified in this config (e.g. 10ftm). minimum-gas-prices = ""
~/.xard/config/xard.toml file and make the following changes
# Time to wait before flushing messages out on the connection flush_throttle_timeout = "25ms"
timeout_propose = "2s" timeout_propose_delta = "500ms" timeout_prevote = "1s" timeout_prevote_delta = "500ms" timeout_precommit = "1s" timeout_precommit_delta = "500ms" timeout_commit = "1s"
# Reactor sleep duration parameters peer_gossip_sleep_duration = "25ms"
flush_throttle_timeout should be set to 25ms timeout_propose should be set to 2s timeout_commit should be set to 1s peer_gossip_sleep_duration should be set to 25ms
See the genesis repo for an example config.toml
Your full node has been initialized!
Fetch the mainnet’s
genesis.json file into
xard’s config directory.
mkdir -p $HOME/.xard/config curl https://raw.githubusercontent.com/xar-network/genesis/master/genesis.json > $HOME/.xard/config/genesis.json
Note we use the
latest directory in the launch repo which contains details for the mainnet like the latest version and the genesis file.
::: tip If you want to connect to the public testnet instead, click here :::
To verify the correctness of the configuration run:
Your node needs to know how to find peers. You’ll need to add healthy seed nodes to
On Xar Hub mainnet, the accepted denom is
1ftm = 1.000.000uftm
Transactions on the 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:
fees = ceil(gas * gasPrices)
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.025uftm, but you might want to change it later.
Start the full node with this command:
Check that everything is running smoothly:
Xar can dump the entire application state to a JSON file, which could be useful for manual analysis and can also be used as the genesis file of a new network.
Export state with:
xard export > [filename].json
You can also export state from a particular height (at the end of processing the block of that height):
xard export --height [height] > [filename].json
If you plan to start a new network from the exported state, export with the
xard export --height [height] --for-zero-height > [filename].json
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 ftms 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:
xard start --assert-invariants-blockly
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:
invariant broken: loose token invariance: pool.NotBondedTokens: 100 sum of account tokens: 101 CRITICAL please submit the following transaction: xarcli tx crisis invariant-broken staking supply
When submitting a invariant-broken transaction, transaction fee tokens are not deducted as the blockchain will halt (aka. this is a free transaction).
You now have an active full node. What’s the next step? You can upgrade your full node to become a Cosmos Validator. The top 100 validators have the ability to propose new blocks to the Cosmos Hub. Continue onto the Validator Setup.