This article was first published on Zilliqa — Official Blog - Medium
Zilliqa Technical Update 13 August 2019 — Strengthening our Mainnet: an in-depth report
Zilliqa is always happy to witness instances where our technology is in high use and demand. Recently, we experienced an all-time high on number of smart contract transactions on our blockchain as Unstoppable Domains went live on July 9th, 2019 receiving overwhelming demand from the community.
Such an event also creates heavy smart contract processing requirements on the Zilliqa mainnet. In this case, it resulted in a few incidents of instability. This technical update addresses these recent issues, outlines the fixes implemented, and upcoming technical enhancements which will strengthen our mainnet. After all, as we’ve always said, constant enrichment of the platform is key to growth and development.
Understanding smart contract states
Every smart contract has its own state. For instance, let’s have a crowdfunding smart contract that records each donor’s contribution. A simple smart contract state can be represented as follows:
As long as the crowdfunding contract is still accepting new donors’ contributions, we can expect it to grow bigger with time.
As you can see, the smart contract state is expected to grow bigger over time. Generally, we expect most smart contracts to perform reasonably fast on Zilliqa mainnet. However, Unstoppable Domains state size has increased very rapidly, resulting in stalled network availability on our blockchain while processing these smart contract transactions.
In the Zilliqa blockchain, there are a few instances when smart contract processing is cut off:
- When the gas limit of a microblock is reached
- When the time limit for transaction processing for a microblock is reached
In this case…
- As the Unstoppable Domains smart contract state grew, we noticed a linear increase in the time needed to process each transaction. It was observed that the smart contract processing time increased from negligible processing time to 500ms, 700ms and finally exceeding ...
To keep reading, please go to the original article at:
Zilliqa — Official Blog - Medium