ZVChain MainNet v1.0.8 Update highlights
⏰⏰⏰ [V1.0.8 version effective reminder]
⚠️⚠️⚠️ The v1.0.8 version will take effect today. It is expected to take effect at 2 pm GMT+8 time zone and the effective height is block 4945537. This version is a necessary upgrade version. All nodes need to complete the upgrade action. Un-upgraded nodes will generate card blocks The problem seriously affects mining revenue.
Miners, please complete the upgrade as soon as possible.
ZVChain MainNet v1.0.8 release highlights
ZVChain is using Chiron’s underlying technology ushered in the 8th iteration; Version number v1.0.8! This version is a necessary upgrade. The community voting results of the “ZVC Stake Return Cycle” ending at 24:00 on March 11th will also be updated and released in this version of the consensus agreement.
The following is the main content of V1.0.8 release.
- Consensus Protocol Enhancement
Optimize known block skipping problems;
Optimization of smart contract execution performance;
The return time after the reduction of the stake amount adjusted from 2 days to 90 days.
Note: The effective height of the consensus optimization is block 4945537, and the time is about 14:00 on March 16, 2020.
2. Add offline data pruning unction新增离线数据剪裁功能
V1.0.7 is an important version for data pruning, which saves a lot of storage for miners. However as time goes by, historical data will still start to accumulate in the miner’s disk. In order to achieve a complete pruning effect and free up more disk storage, V1.0.8 version also introduced offline pruning function. Miners can use this feature to further free up space and save disk costs.
To use the offline trimming function, you must first stop the process. After stopping, select the corresponding command to execute according to your system.
Linux (mac) system: ./gzv prune — db = d_b — sdb = d_small — cpu 2 — mem = 2048 — out = prune-verify-log — cachedir = cache_store
windows system: gzv.exe prune — db = d_b — sdb = d_small — cpu 2 — mem = 2048 — out = prune-verify-log — cachedir = cache_store
Explanation of the above example command:
— db = d_b: The directory where d_b is located, the example is the same directory as gzv
— sdb = d_small: The directory where d_small is located, the example is the same directory as gzv
— cpu 2: Select the core according to the situation of the machine Number (the number of CPU cores, the more the number of cores, the higher the pruning efficiency)
— mem = 2048: select the memory according to the situation of the own machine (the memory can be the default)
— out = prune-verify-log: log output command for viewing specific execution progress
In order for you to understand the effect of the offline pruning function more intuitively, we have tested some machines. Take 4.5 million pieces of data as an example. The total amount of data of 4.5 million pieces is about 250G. Using a V1.0.7 pruned version, synchronize from 0 to 4.5 million pieces of height about 25G. Using the offline pruning tool under V1.0.8, the data size will be reduced further to 12G.
Pruning time depends on the performance of the machine, the following data is for reference only.
Based on the above, miners can choose offline pruning based on the 250G ledger, or offline pruning based on the 25G pruning version to achieve the effect of complete pruning.
As the offline tailoring function requires a certain amount of physical resources, we recommend that it will be best executed on an idle machine to avoid affecting the normal mining of other nodes. Please wait patiently when pruning. If there is any abnormal situation such as power failure or downtime during the period, you can execute the above command to continue pruning or execute the mining command to continue mining.
v1.0.8 upgrade steps
Method 1: There are an “updater” file upgrade methods as follows
Step 1: Is there an “updater” File. Check the “original folder”, the first stop any running digging: The first step in mining programs;
Step 2: Run the “updater” file to complete the upgrade, and continue to run the mining program after the upgrade is complete.
Method 2: If there is no “updater” file, please complete the upgrade according to the following process.
Step 1: Visit the official website to download the latest program and extract.
Step 2: Stop running your current mining program, upgrade the new package of “gzv” file into the original folder. For windows, just drop the new “gzv” and “p2p_core “.dll” files into the original folder to overwrite.
Step 3: Run the new mining program as usual (seen in this following video, using the windows system as example).
This release is an update of the consensus protocol. All nodes need to complete the upgrade action. Nodes that are not upgraded will cause block problems, which will seriously affect mining revenue.