Network Selection
Choosing Mainnet and Testnet.
To facilitate the development and testing of new features and prevent irreversible damage from deploying contracts or code on the production network, MVC nodes support two types of networks: the mainnet and the testnet. The mainnet is the real blockchain network where SPACE and tokens have actual value, while the testnet is a blockchain network used for development and testing, where SPACE and tokens are solely for development and testing purposes.
Note: Do not deploy contracts or code on the testnet, as the SPACE and tokens there are for development and testing only and do not have real value. Additionally, data on the testnet may be reset.
By adjusting the node's startup configuration settings (mvc.conf), you can choose to connect to either the mainnet or the testnet. By default, the node and client connect to the mainnet. Key configurations include:
testnet=0: 0 indicates connection to the mainnet, 1 indicates connection to the testnet.
addnode: Addresses of seed nodes for the mainnet and testnet, which can help you quickly find other nodes and start synchronizing blocks.
init params: Initial parameters for the mainnet and testnet, including initial rewards, halving cycles, genesis block locking scripts, etc. (basic genesis consensus).
Mainnet Configuration
Configure the following in the mvc.conf
file and start:
The current status of the mainnet can be viewed through the MvcScan mainnet browser.
Testnet Configuration
Currently, MVC uses a testnet called testnet3
, and more testnets may be expanded in the future based on needs. Configure the following in the mvc.conf
file and start:
The current status of the testnet can be viewed through the MvcScan testnet browser.
If you need testnet SPACE for testing, you can run your own testnet node mining to obtain test coins, or refer to applying for a test coin faucet.