Zilliqa Mainnet Updates

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.

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.

Hi all,

The client release for v4.6.0 will be ready to be downloaded by 7th May 2019 UTC 11:00 hrs. Please note that v4.6.0 is backwards compatible with v4.5.0. However, it is still recommended for all nodes to upgrade to the v4.6.0 client for optimised performance.

: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.6.0, please follow this guide above.

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


Release notes for v4.6.0:

  • Upgraded scilla binary to v0.3.0
  • Auto-rejoining capability for seed nodes
  • DS microblock storage and processing fix
  • Transaction packet shard assignment fix
  • Separate server port for miner API
  • Security fixes

Hi all,

As you may know, smart contracts will be enabled for v4.6.x (current version of mainnet) with scilla binary v.0.3.0 on the 10th June 2019. We will be proceeding to do rolling upgrades on the Seed nodes to change their configuration settings. Please note that the public API service (https://api.zilliqa.com) will be down from UTC 03:00 to 06:00 hrs to perform this upgrade. Hence, during this upgrading phase, transactions will not go through.

Please note that the version of your mining CPU nodes remains as per v4.6.x and the scilla binary is still v0.3.0. There will be NO ACTION required from your end unless you are using an older version of the software than the ones stated above. Thank you everyone for your support.

Hi all,

The network is experiencing continuous view changes as a result of connection limit issue.
Please note that a network recovery for v4.6.1 will happen on 9th June 2019 at UTC 03:30 hrs.

Please do note that this will mean all nodes will have to rejoin the network to perform this recovery.
You need to download a new configuration file with the updated settings in the constants.xml file.
The configuration files for v4.6.1 will ready to be downloaded by UTC 10: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.6.1, please follow the guide above.

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

Hi all,

Due to longer than expected data synchronization, Zilliqa’s network recovery maintenance for v4.6.1 will be extended by another 6 hours to 9th June 2019 UTC 16:00. Our team is working hard to complete the recovery as quickly as possible.

Another announcement will be made once the recovery is complete. We apologize for any inconvenience caused, and thank you for your patience.

The network recovery for version tag v4.6.1 has been completed as of 9th June 2019 UTC 13:40 hrs. The configuration files for v4.6.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.6.1 configuration files to join the recovered Zilliqa mainnet. Thank you for your support!

Please see the guide above to find out how to complete a clean recovery if you are using docker build.

Hi all,

We received an alert on the continuous View change issue that the Zilliqa mainnet is facing as of UTC 03:00 hrs (15th July), we are currently investigating the root cause and deploying a fix to resume the consensus for block propagation. We kindly request you to bear with us before we issue a patch for this fix. We will inform everyone along the way when the update is available.

Regards,
Zilliqa Team

1 Like

The network recovery and upgrade to version tag v4.7.0 has been completed as of 16th July 2019 05:00 hrs (UTC). The configuration files for v4.7.0 are now ready to be downloaded. The root cause of this issue is due to an unexpected edge case of smart contract transactions flooding the network at the block height 170901, we did a hotfix to this issue by lowering the micro-block gas limit from 500k -> 300k to increase the safety margin. The network should function as it were before now, and smart contract transactions should resume as per normal.

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

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

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

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


Release notes for v4.7.0 :

New Features & Improvements

  • Development/build-related changes
    • Use Travis native Ubuntu 16.04 (#1647)
    • Fix issues reported by cppcheck (#1652)
    • Standardize Include Guards (#1653)
    • Add more Clang Tidy checks (#1654)
    • Protect destructors of some template classes (#1655)
    • Standardize Include Guard Check (#1657)
    • Add pedantic flag to compiler options (#1659)
    • Fix some uninitialized params & Remove explicit copy constructor for std::move (#1660)
    • Add SECURITY.MD (#1670)
    • Add few essential MD files (#1671)
  • Functional improvements
    • Increase max peer connection (#1662)
    • Remove redundant pow test case (#1676)
    • Add retry mechanism for send pow to proxy (#1683)
    • Add log for txn hash (#1692)
    • Add epoch num to GetNodeType (#1695)
    • log popen failure (#1712)
    • Node only do sync if failed to do pow (#1707)

Bug Fixes

  • Functional bug fixes
    • Handle peer connection counter correctly (#1663)
    • Stop lookup api server when it is synchronizing (#1677)
    • clear peer counter (#1689)
    • Remove IP check on VC (#1690)
    • Fix log messages for address (#1710)
    • Check whether account exists when create contract (#1714)
    • Fix epochfin for lookup when no shard formed (#1709)
    • Continue check result from proxy until timeout (#1706)
  • Infrastructure bug fixes
    • Fetch constant file from dsguard instead of normal node (#1679)
    • Fix of kubectl cp command (#1713)

Hi all,

We received a stall alert on the Zilliqa mainnet as of UTC 04:45 hrs (20th July) , we are currently investigating the root cause and in the midst of deploying a fix to resume the consensus for block propagation. We kindly request you to bear with us before we issue a patch for this fix. We will inform everyone along the way when the update is available.

Regards,
Zilliqa Team

Hi all,

Thank you for your patience! The network recovery has been completed as of 20th July 2019 09:15 hrs (UTC). We will be rolling new enhancements to the protocol in the coming weeks to address the address the issues encountered today.

The new configuration files for v4.7.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 new v4.7.0 configuration files to join the recovered Zilliqa mainnet. Thank you for your support!

Dear community members,

We will be conducting a network upgrade to version tag v4.7.1 on the 30th July 2019 from UTC 03:00 to 06:00 hrs to further improve the stability of the network. Please note that this will mean all nodes will have to rejoin the network to perform this upgrade.

The new configuration files for v4.7.1 is expected to be ready for downloaded by 30th July 2019 06:00hrs.

: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 conduct a clean upgrade to v4.7.1, please follow this forum guide above.

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


Release notes for v4.7.1:

  • MICROBLOCK_GAS_LIMIT changed to 15000
  • MAX_GOSSIP_MSG_SIZE_IN_BYTES changed to 8000000
  • Some bug fixes…

The network upgrade to version tag v4.7.1 has been completed as of 30th July 2019 04:20 hrs (UTC). The configuration files for v4.7.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.7.1 docker image or native build, and use the latest v4.7.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.7.1, please follow the guide above.

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

Dear community,

We received an alert the Zilliqa mainnet is not progressing well as of UTC 03:45 hrs (7 Aug). We will proceed to conduct a network recovery with some new fixes.

We will inform everyone once the issue is resolved. Thanks for your patience and understanding.

Thanks,
Zilliqa Team

1 Like

The network recovery and upgrade to version tag v4.7.2 has been completed as of 7th August 2019 09:00 hrs (UTC). The configuration files for v4.7.2 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.7.2 docker image or native build, and use the latest v4.7.2 configuration files to join the upgraded Zilliqa mainnet. Thank you for your continuous support.

To ensure that you have completed a clean upgrade to v4.7.2, please follow the guide linked below:

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

Release note can be found at: https://github.com/Zilliqa/Zilliqa/releases/tag/v4.7.2

The network upgrade to version tag v4.8.0 has been completed as of 15th August 2019 08:10 hrs (UTC). The configuration files for v4.8.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.8.0 docker image or native build, and use the latest v4.8.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.8.0, please follow the guide above.

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

Release note can be found at: https://github.com/Zilliqa/Zilliqa/releases/tag/v4.8.0

Dear community members,

We will be conducting a network upgrade to version tag v5.0.0 on the 12th September 2019 from UTC 09:00 to 12:00 hrs. This will be the first major release of Zilliqa since mainnet is launched. Features such as Scilla IPC, efficient state access and DS reputation will be introduced in this release. This release will also include stability fixes.

Please note that all nodes will have to rejoin the network to perform this upgrade.

The new configuration files for v5.0.0 is expected to be ready for download by 12th September 2019 UTC 12:00hrs.

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

Do note that during the upgrade period, no transaction will be processed by the network.

To conduct a clean upgrade to v5.0.0, please follow this forum guide above.

When you have successfully upgraded your node, you will be welcomed with a message: “The latest software tag: v5.0.0” in the zilliqa-log textfile. Thank you for your continued support!

The network upgrade to version tag v5.0.0 has been completed as of 12th September 2019 15:00 hrs (UTC). The configuration files for v5.0.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 v5.0.0 docker image or native build, and use the latest v5.0.0 configuration files to join the upgraded Zilliqa mainnet. The configuration file can be found at https://mainnet-join.zilliqa.com/configuration.tar.gz

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

Release note can be found at: https://github.com/Zilliqa/Zilliqa/releases/tag/v5.0.0

Please note that this release also comes with changes to our existing API (e.g., GetSmartContractState, GetTransaction), as well as the addition of new methods (e.g., GetSmartContractSubState, GetTotalCoinSupply). Users can refer to https://apidocs.zilliqa.com/ for more details.