🎁 Zilliqa 1.0 wraps up at block 4770087, with the final new transactions accepted at block 4769950. 🗓️ June 23 kicks off the migration to Zilliqa 2.0 ⛓️ Mainnet launch just a few days after June 23.
Enter Zilliqa 2.0 – Agate Phase with: ⚙️ Scilla ↔ EVM interoperability — build like never before ⚡️Lightening fast block processing with an average block time of around 2 seconds 🛡️ New staking portal — simpler but smarter 📦 Seamless migration — accounts, contracts, blocks, everything moves forward
Zilliqa 2.0 isn’t just an upgrade — it’s a launchpad for the future.
We have noticed an issue with lookup and API nodes going out of sync, which has unfortunately resulted in transactions not reaching the blockchain for processing.
We will be restoring the Zilliqa network now to fix this issue. Please note that the network will not be processing transactions during this time.
We appreciate your patience and deeply regret any inconvenience this may cause. Rest assured, our team is working tirelessly to resolve the issue as swiftly as possible.
Note - Funds are SAFU. If you don't see funds in your wallet, you can always verify them on-chain by going to https://t.co/jUjlVTsEgE. Input your ZIL address in the search box and click Enter to view your balance and transaction history.
We would like to inform the community, ecosystem partners and exchanges that a scheduled maintenance will take place on Monday, 2nd June at 04:00 AM UTC. This maintenance involves upgrading the underlying infrastructure for Zilliqa 1.0 blockchain nodes deployed in GKE, as the current node pools are approaching end-of-support status.
🕒 Expected downtime: Approximately 12 hours
⚠️ Please note: This is an infrastructure-only upgrade. No changes will be made to the blockchain version.
We appreciate your understanding and will provide updates as the maintenance progresses. If you have any questions or require further details, please don’t hesitate to reach out.
✅ The first full rehearsal of a Zilliqa 2.0 network launch has been successfully completed. Additional rehearsals for both the mainnet and testnet are scheduled for the upcoming weekend to further validate system readiness.
🗓 The release of version 0.9.0 has been rescheduled for this week following the discovery of issues during the migration to the new redb database. These are currently being addressed to ensure stability and performance.
🛡️ The Hacken bug bounty program concludes today. Several new reports were submitted yesterday and are under active review by the security team. Relevant findings will be disclosed in accordance with our responsible disclosure process.
🧪 During extensive testing of reward claiming on Zillion, expensive Scilla transactions significantly impacted block production. As observed on the proto-mainnet, such transactions can lead to the temporary stalling of the network. This Scilla-related issue is a significant risk that directly affects the planned mainnet migration date.
⚠️ The current assessment is that the Zilliqa 2.0 mainnet launch may need to be postponed by one week unless a solution to this issue is implemented by the end of this week.
We appreciate the community's continued support and will provide further updates as progress continues.
Have questions about the upcoming migration to Zilliqa 2.0?
Check out the FAQs on our Zilliqa 2.0 roadmap site — covering everything from the switchover date to token compatibility: https://roadmap.zilliqa.com/zilliqa-2-0-faq
Leadership update: After serving as CFO for 3 years, Alexander Zahnd has now stepped in as interim CEO of Zilliqa following the recent departure of Matt Dyer.
“I am grateful for Matt’s contributions, and want to reiterate that our focus remains on driving ahead towards Zilliqa 2.0. Thank you for your continued support” - Alexander Zahnd (@0xCypherPeak).