- Linux system required
- Public IP address required
- Ubuntu 14.04 64bit OS recommended
- Above dual-core CPU recommended
- Above 2 GB RAM recommended
- Above 2MB broadwidth recommended
There are two seperated systems: test version (testnet) and main official version (mainnet). Both of them are co-existed but unable to communicate with each other.
The installation procedures of these two systems are the same except the installation package and configuration file (including default port setting).
As long as there is no conflict of ports, you can install the test version and official version on the same compouter, but please note, the power of the computer is highly required, such as dual-core CPU, 2GB RAM above or at least 4MB brandwidth…
For test version (testnet)
tar zxvf asch-linux-latest-testnet.tar.gz
For official version (mainnet)
tar zxvf asch-linux-latest-mainnet.tar.gz
Usually, the version number of testnet will larger than that of mainnet.
In this step, two steps will be done automatically, as follows:
- Install some dependency modules like nodejs and sqlite3
- Install and configure the ntp service by which to synchronize your system time can be synchronized with that of other nodes.
This step only need be executed once, but it is OK to be done for several times.
Go to your installation folder
Go to the installation folder
To start the service
To stop the service
To check the running status
To restart the service
To upgrade the system
To re-synchronize the blockchain
To check the system version
To start producing block
./aschd enable “your sercret”
To check the log
tail -f logs/debug.log
Use your favorite editor to open config.json and locate find the [secret] field. Fill this field with your delegate’s password. This field is an array of JSON format strings, which means you can set several passwords in one particular computer, but be careful not to duplicate them.
NOTICE: DO NOT configure the same password, no matter in a single machine computer or in multiple machinescomputers.
By default, the system will automatically detect the public IP you assigned automatically. But in some Cloud hostshost built on cloud, the public IP may not be able to identifiedidentify. Under such circumstanceIn this situation, the following field needs to be appended in config.json:
“publicIp”: “Here is your public IP”,
And don’t forget to restarting your system after configuration by:
Check the [port] field in config.json, the default port numbers of testnet and mainnet are 4096 and 8192, respectively.
Check whether the service server is runningstarted by typing commands as follows:
Failed to load delegates: Account xxxxxxxxx not found
It means that the passphrase of your account has not been registered as a delegate yet, or you started the service before it registered as a delegate. Simply restarting the service will solve the problem.
NOTICE: If your node is synchronizing the blocks, restart the system after the synchronization is finished.
If the system has been restarted successfully, the following log will be found:
grep Forging logs/debug.log
Forging enabled on account: xxxxxxxxxxxxxx
This issue can be confirmed by comparing the block height of your wallet and official node
First, try to restart the system:
If problem is still unsolved, try to rebuild`