- Zilliqa has announced the launch of smart contracts on June 10
- In the past 2 weeks the team introduced a series of bug fixes and improvements to Zilliqa
- The Scilla programming language is being updated as well
According to an announcement made by Zilliqa project in their official blog, smart contracts will be activated on their mainnet on June 10. This announcement falls in line with the promises the project made two years ago. Since then, it has made major progress and created a variety of partnerships. Prior to launch, the team decided to highlight all the latest improvements that have been made both to the Zilliqa code and the Zilliqa-developed Scilla smart contract language.
Zilliqa codes changes aimed at stability and security
Changes made to the Zilliqa core are mostly minor but nevertheless important, because they are enhancing its stability and security. Here are some of these changes:
- Enforcement of infrastructure isolation – in short, this improves the security by isolating the most important systems in the infrastructure from the less important ones. This way, even if a vulnerability is discovered in one of the systems that is not one of the most important, it does not compromise the safety of the whole system.
- Improved metadata persistence – a small but important bug fix which eliminates the potential possibility of metadata loss that can only be fixed by human intervention. Thankfully, the bug was fixed before any such accidents happened.
Scilla programming language expanded
Also excitingly, the Scilla language received some major changes. These features that the team has been working on for the past two years are crucial for the correct working of smart contracts. Because of that, improving Scilla has been a priority for the team.
Two major features have been introduced:
- Formal verification – thanks to the formalized integer safe arithmetic the system is now less vulnerable to so-called overflow and underflow attacks which allowed attackers to receive unexpectedly large amount of funds to their wallet.
- Procedures – these are crucial for the correct work of smart contracts. Main aim of the procedure is to share select bits of code, allowing different parts of each smart contract’s state to stay in sync. An example of use case would be standartisation of error messaging.