# Join the BitSong Network Public Testnet
See the networks repo for information on the testnet, including the correct version of the
go-bitsong to use and details about the genesis file.
You need to install go-bitsong before you go further
# Setting Up a New Node
These instructions are for setting up a brand new full node from scratch.
First, initialize the node and create the necessary config files:
bitsongd init <your_custom_moniker> --chain-id=bitsong-testnet-3
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
~/.bitsongd/config/app.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. 10ubtsg). minimum-gas-prices = ""
Your full node has been initialized!
# Genesis & Seeds
# Copy the Genesis File
Fetch the testnet's
genesis.json file into
bitsongd's config directory.
mkdir -p $HOME/.bitsongd/config curl https://raw.githubusercontent.com/bitsongofficial/networks/master/bitsong-testnet-3/genesis.json > $HOME/.bitsongd/config/genesis.json
Note we use the
latest directory in the
bitsong-testnet-3 repo which contains details for the testnet like the latest version and the genesis file.
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
bitsong-testnet-3 repo repo contains links to some seed nodes.
You can also ask for peers on the Validators Discord Chat
For more information on seeds and peers, you can read this.
# A Note on Gas and Fees
On BitSong Network, the accepted denom is
1btsg = 1.000.000ubtsg
Transactions on the BitSong 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.025ubtsg, but you might want to change it later.
# 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 BitSong Testnet Explorer.
# Export State
go-bitsong 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:
bitsongd export > [filename].json
You can also export state from a particular height (at the end of processing the block of that height):
bitsongd export --height [height] > [filename].json
If you plan to start a new network from the exported state, export with the
bitsongd export --height [height] --for-zero-height > [filename].json
# Upgrade to Validator Node
You now have an active full node. What's the next step? You can upgrade your full node to become a BitSong Validator. The top 32 validators have the ability to propose new blocks to the BitSong Network. Continue onto the Validator Setup.