Zilliqa Mainnet Updates

This thread is meant to be a consolidation of all updates happening or has happened to Zilliqa mainnet. You may also track the mainnet status in the status board below.

Please subscribe to this topic by “Watching” it. You will receive email updates whenever this thread is updated with new live updates of the Zilliqa network client. Thank you for your support.

Mainnet status board:

Current version is v4.6.1.

Legend:
:white_check_mark: Operational
:exclamation: Alert
:arrows_counterclockwise: Update-in-progress

Other useful links:

Steps for performing a clean upgrade for miners:

  1. Backup your mykey.txt file in your current “join” folder to a safe location.
  2. Clean up the docker images to reclaim the disk space:
    sudo docker stop zilliqa
    sudo docker system prune # remove all previous container data
    sudo docker images # list all existing images
    sudo docker rmi INSERT_DOCKER_IMAGE_NUMBER_HERE # remove specific old zilliqa image
    
  3. Delete your current “join” folder:
    cd Desktop && sudo rm -rf join
    
  4. Create a new “join” folder and download the latest configuration files:
    mkdir join && cd join
    wget https://mainnet-join.zilliqa.com/configuration.tar.gz && tar zxvf configuration.tar.gz
    
  5. Put your mykey.txt file in the newly created “join” folder.
  6. Edit your constants.xml file to the configuration you desired for local CPU or local Nvidia GPU or remote mining:
    • For local CPU mining, no change is required.
    • For local Nvidia GPU mining, change the following parameters:
      <CUDA_GPU_MINE>true</CUDA_GPU_MINE>
      
    • For remote mining (via Zilminer), change the following parameters:
      <GETWORK_SERVER_MINE >true</GETWORK_SERVER_MINE>
      <GETWORK_SERVER_PORT>4202</GETWORK_SERVER_PORT> # or any other preferred ports
      <FULL_DATASET_MINE>false</FULL_DATASET_MINE>
      
  7. Get your system IP address:
    curl https://ipinfo.io/ip
    
  8. Relaunch the docker image:
    ./launch_docker.sh # add the --cuda flag if you are mining locally with Nvidia GPUs
    

Steps for performing a clean upgrade for seed nodes:

  1. Backup your verifier.txt file in your current “my_seed” folder to a safe location.

  2. Clean up the docker images to reclaim the disk space:

    sudo docker stop zilliqa
    sudo docker system prune # remove all previous container data
    sudo docker images # list all existing images
    sudo docker rmi INSERT_DOCKER_IMAGE_NUMBER_HERE # remove specific old zilliqa image
    
  3. Delete your current “my_seed” folder:

    cd Desktop && sudo rm -rf my_seed
    
  4. Create a new “my_seed” folder and download the latest configuration files:

    mkdir my_seed && cd my_seed
    wget https://mainnet-seedjoin.zilliqa.com/configuration.tar.gz
    tar zxvf configuration.tar.gz
    
  5. Put your verifier.txt file in the newly created “my_seed” folder.

  6. Reconfigure the node settings and rejoin the network by following instructions found here:
    https://zilliqa.github.io/dev-portal/docs/en/exchange-getting-started#configuring-the-node

1 Like

The network upgrade to version tag v4.1.1 has been completed as of 22nd February 2019 09:30 hrs (UTC). The configuration files for v4.1.1 are ready to be downloaded now.

Please make sure to use the v4.1.1 docker image or native build, and use the latest v4.1.1 configuration files to join the upgraded Zilliqa mainnet. Thank you for your support.


Release notes for v4.1.1:

  • Fix memory leak
  • Additional checks for foreign messages
  • Consensus check fix
  • Revert socket PR that causes stall
  • Check vacuous epoch during recovery

Hi all,

The network upgrade to v4.2.0 will happen on 1st March 2019 from UTC 03:00 to 05:00 hrs. (One DS epoch worth of buffer time) Please note that this will mean all nodes will have to rejoin the network to perform this upgrade.

The configuration files for v4.2.0 will ready to be downloaded by UTC 05:00 hrs.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

To ensure that you have completed a clean upgrade to v4.2.0, please follow this guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.2.0” in the zilliqa-log textfile.


Announcement for bootstrap extension:


Release notes for v4.2.0 :

  • Added checks for PoW submission (IP mismatch and submission count)
  • Added checks for target epoch/difficulty for transaction processing
  • Added check for IP in consensus commit and response messages
  • Revised strict enforcement of Zilliqa latest version
  • Fixed PoW mining window for DS difficulty
  • Fixed timing of processing consensus messages against state transitions
  • Fixed seed node joining issue due to missing sharding structure
  • Revised the target DS epoch number

The network upgrade to version tag v4.2.0 has been completed as of 1st March 2019 04:30 hrs (UTC) . The configuration files for v4.2.0 are ready to be downloaded now.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

Please make sure to use the v4.2.0 docker image or native build, and use the latest v4.2.0 configuration files to join the upgraded Zilliqa mainnet. Thank you for your support.

To ensure that you have completed a clean upgrade to v4.2.0, please follow the guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.2.0” in the zilliqa-log textfile.


Release notes for v4.2.0 :

  • Added checks for PoW submission (IP mismatch and submission count)
  • Added checks for target epoch/difficulty for transaction processing
  • Added check for IP in consensus commit and response messages
  • Revised strict enforcement of Zilliqa latest version
  • Fixed PoW mining window for DS difficulty
  • Fixed timing of processing consensus messages against state transitions
  • Fixed seed node joining issue due to missing sharding structure
  • Revised the target DS epoch number

Hi all,

The network upgrade to v4.3.0 will happen on 13th March 2019 from UTC 06:00 to 08:00 hrs. (One DS epoch worth of buffer time) Please note that this will mean all nodes will have to rejoin the network to perform this upgrade.

The configuration files for v4.3.0 will ready to be downloaded by UTC 08:00 hrs.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

To ensure that you have completed a clean upgrade to v4.3.0 , please follow this guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.3.0” in the zilliqa-log textfile.


Release notes for v4.3.0 :

  • Fixed node sync type initialization
  • Fixed lookup node rewarding
  • Fixed invalid signature for remote mining (credit: @deepgully)
  • Coinbase performance optimization
  • Security updates
  • Reduction of Shard Guard nodes (from 1200 to 700)
1 Like

The network upgrade to version tag v4.30 has been completed as of 13 March 2019 09:00 hrs (UTC) . The configuration files for v4.3.0 are now ready to be downloaded.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

Please make sure to use the v4.3.0 docker image or native build, and use the latest v4.3.0 configuration files to join the upgraded Zilliqa mainnet. Thank you for your support.

To ensure that you have completed a clean upgrade to v4.3.0, please follow the guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.3.0” in the zilliqa-log textfile.


Release notes for v4.3.0 :

  • Fixed node sync type initialization
  • Fixed lookup node rewarding
  • Fixed invalid signature for remote mining (credit: @deepgully)
  • Coinbase performance optimization
  • Security updates
  • Reduction of Shard Guard nodes (from 1200 to 700 )

Hi all,

The network was currently experiencing continuous view changes as a result of multiple DS nodes being out-of-sync. Therefore, we have planned a manual recovery of the mainnet. We will continue to monitor the logs of this incident to find out the root cause and issue a patch in the relative near future.

This recovery process is similar to the upgrading process, except that there will be no version update to the network clients. However, you will still need to download a new configuration file with the renewed IP settings in the constants.xml file.

Please note that the network recovery for v4.3.0 will happen on 17th March 2019 at UTC 07:00 hrs. Please do note that this will mean all nodes will have to rejoin the network to perform this recovery.

The configuration files for v4.3.0 will ready to be downloaded by UTC 07:00 hrs.

:exclamation: Please remember to save your mykey.txt as usual before carrying out this recovery process. :exclamation:

To ensure that you have completed a clean recovery for v4.3.0, please follow this guide above.

When you successfully recovered your node, you will be revisited with a message: “The latest software tag: v4.3.0” in the zilliqa-log textfile.

Hi all,

The network upgrade to v4.3.1 will happen on 18th March 2019 from UTC 07:00 to 09:00 hrs. (One DS epoch worth of buffer time) Please note that this will mean all nodes will have to rejoin the network to perform this upgrade.

The configuration files for v4.3.1 will ready to be downloaded by UTC 09:00 hrs.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

To ensure that you have completed a clean upgrade to v4.3.1 , please follow this guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.3.1” in the zilliqa-log textfile.


Release notes for v4.3.1 :

  • Increase COMMIT_WINDOW_IN_SECONDS to 50 seconds
  • Increase ANNOUNCEMENT_DELAY_IN_MS to 10 seconds
  • Increase TX_DISTRIBUTE_TIME_IN_MS to 40 seconds
2 Likes

The network upgrade to version tag v4.31 has been completed as of 18 March 2019 08:00 hrs (UTC) . The configuration files for v4.3.1 are now ready to be downloaded.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

Please make sure to use the v4.3.1 docker image or native build, and use the latest v4.3.1 configuration files to join the upgraded Zilliqa mainnet. Thank you for your support.

To ensure that you have completed a clean upgrade to v4.3.1 , please follow the guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.3.1” in the zilliqa-log textfile.


Release notes for v4.3.1 :

  • Increase COMMIT_WINDOW_IN_SECONDS to 50 seconds
  • Increase ANNOUNCEMENT_DELAY_IN_MS to 10 seconds
  • Increase TX_DISTRIBUTE_TIME_IN_MS to 40 seconds

Hi all,

The network was currently experiencing continuous view changes as a result of multiple DS nodes being out-of-sync. Therefore, we have planned a manual recovery of the mainnet. We will continue to monitor the logs of this incident to find out the root cause and issue a patch.

This recovery process is similar to the upgrading process, except that there will be no version update to the network clients. However, you will still need to download a new configuration file with the renewed IP settings in the constants.xml file.

Please note that the network recovery for v4.3.1 will happen on 26th March 2019 at UTC 11:00 hrs. Please do note that this will mean all nodes will have to rejoin the network to perform this recovery.

The configuration files for v4.3.1 will ready to be downloaded by UTC 11:00 hrs .

:exclamation: Please remember to save your mykey.txt as usual before carrying out this recovery process. :exclamation:

To ensure that you have completed a clean recovery for v4.3.1, please follow this guide above.

When you successfully recovered your node, you will be revisited with a message: “The latest software tag: v4.3.1” in the zilliqa-log textfile.

The network recovery for version tag v4.3.1 has been completed as of 26 March 2019 10:20 hrs (UTC) . The configuration files for v4.3.1 are now ready to be downloaded.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

Please make sure to use the latest v4.3.1 configuration files to join the recovered Zilliqa mainnet. Thank you for your support.

Hi all,

The network upgrade to v4.4.0 will happen on 30th March 2019 from UTC 6:00 to 08:00 hrs . (One DS epoch worth of buffer time) Please note that this will mean all nodes will have to rejoin the network to perform this upgrade.

The configuration files for v4.4.0 will ready to be downloaded by UTC 08:00 hrs .

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

To ensure that you have completed a clean upgrade to v4.4.0, please follow this guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.4.0” in the zilliqa-log textfile.


Release notes for v4.4.0:

  • Periodic merkle trie re-population to reduce disk usage consumption
  • New synchronisation method using incremental DB design
  • New difficulty adjustment algorithm to have more linear hashrate growth
  • More robust network requirement with new blacklisting mechanism
  • Toggle option of processing smart contracts
  • Better concurrency handling in BlockStorage
  • ZilliqaDaemon will now wait for Zilliqa process to start instead of exiting
  • New status RPC to allow for local query of blockchain information
  • View change integration test adjustment
  • Other minor functional and security fixes
1 Like

The network upgrade to version tag v4.4.0 has been completed as of 30 March 2019 06:00 hrs (UTC). The configuration files for v4.4.0 are now ready to be downloaded.

:exclamation: Please remember to save your mykey.txt as usual before carrying out any upgrade. :exclamation:

Please make sure to use the v4.4.0 docker image or native build, and use the latest v4.4.0 configuration files to join the upgraded Zilliqa mainnet. Thank you for your support.

To ensure that you have completed a clean upgrade to v4.4.0, please follow the guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.4.0” in the zilliqa-log textfile.


Release notes for v4.4.0 :

  • Periodic merkle trie re-population to reduce disk usage consumption
  • New synchronisation method using incremental DB design
  • New difficulty adjustment algorithm to have more linear hashrate growth
  • More robust network requirement with new blacklisting mechanism
  • Toggle option of processing smart contracts
  • Better concurrency handling in BlockStorage
  • ZilliqaDaemon will now wait for Zilliqa process to start instead of exiting
  • New status RPC to allow for local query of blockchain information
  • View change integration test adjustment
  • Other minor functional and security fixes

Hi all,

The client release for v4.4.1 will be ready to be downloaded by 1st April 2019 UTC 13:00 hrs. Please note that v4.4.1 is backwards compatible with v4.4.0. However, it is still recommended for all nodes to upgrade to the v4.4.1 client if you are facing the following issues:

  • RejoinAsNormal loop bug leading to zilliqa-log blowup
  • State root hash check bug when syncing new nodes

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

To ensure that you have completed a clean client upgrade to v4.4.1, please follow this guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.4.1” in the zilliqa-log textfile.


Release notes for v4.4.1:

  • Fix Ubuntu 18.04 native build
  • Fix RejoinAsNormal loop bug
  • Fix State root hash check bug
  • Revert blacklist clearing for lookup

Hi all,

The client release for v4.4.1 is ready to be downloaded as of 1st April 2019 UTC 14:00 hrs. Please note that v4.4.1 is backwards compatible with v4.4.0. However, it is still recommended for all nodes to upgrade to the v4.4.1 client if you are facing the following issues:

  • RejoinAsNormal loop bug leading to zilliqa-log blowup
  • State root hash check bug when syncing new nodes

:exclamation:Please remember to save your mykey.txt as usual before carrying out any upgrade.:exclamation:

To ensure that you have completed a clean client upgrade to v4.4.1, please follow this guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.4.1” in the zilliqa-log textfile.


Release notes for v4.4.1:

  • Fix Ubuntu 18.04 native build
  • Fix RejoinAsNormal loop bug
  • Fix State root hash check bug
  • Revert blacklist clearing for lookup

Hi all,

The network upgrade to v4.5.0 will happen on 18th April 2019 from UTC 3:00 to 05:00 hrs . (One DS epoch worth of buffer time) Please note that this will mean all nodes will have to rejoin the network to perform this upgrade.

The configuration files for v4.5.0 will ready to be downloaded by UTC 05:00 hrs.

:exclamation: Please remember to save your mykey.txt as usual before carrying out any upgrade. :exclamation:

Do note that during the upgrade period, all transactions will not be processed by the network.

To ensure that you have completed a clean upgrade to v4.5.0, please follow this guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.5.0” in the zilliqa-log textfile.


Release notes for v4.5.0:

  • PoW verification optimization
  • New miner API for querying transactions
  • New lookup API for querying shard nodes
  • Multiple fixes to node joining and recovery
  • Lookup DNS resolution for transaction forwarding
  • Security fixes

The network upgrade to version tag v4.5.0 has been completed as of 18th April 2019 04:35 hrs (UTC). The configuration files for v4.5.0 are now ready to be downloaded.

:exclamation: Please remember to save your mykey.txt as usual before carrying out any upgrade. :exclamation:

Please make sure to use the v4.5.0 docker image or native build, and use the latest v4.5.0 configuration files to join the upgraded Zilliqa mainnet. Thank you for your support.

To ensure that you have completed a clean upgrade to v4.5.0, please follow the guide above.

When you successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v4.5.0” in the zilliqa-log textfile.


Release notes for v4.5.0 :

  • PoW verification optimisation
  • New miner API for querying transactions
  • New lookup API for querying shard nodes
  • Multiple fixes to node joining and recovery
  • Lookup DNS resolution for transaction forwarding
  • Security fixes

Hi all,

There was mini outage of the network due to lookup nodes being out-of-sync. These lookup nodes has since been recovered and the network has regained full functionality.

Please note that you might be missing a few final TX blocks as they were not fetched by your node while lookup were down. In this case, you will have to rejoin the network, and re-sync your node in order to fetch all TX blocks from archival node.

:exclamation:Please remember to save your mykey.txt as usual before carrying out any recovery.:exclamation:

Please also see the forum guide above to find out how to clean persistence files and rejoin/resync your node properly. Thank you.