The Fourth exchange migration hard fork is scheduled for block height 39,242,023 expected on 30 October 2026 at ~07:00 UTC. This upgrade will: - Migrate XT exchange’s ZIL balances from legacy Schnorr addresses to verified Zilliqa EVM addresses. - Enable validator reward distribution every epoch instead of every block. - Activate Pectra support, updating Zilliqa’s EVM compatibility. - Enable the migration of legacy balances staked on Zilliqa 1 (Scilla staking contract) using the ZKP app. - Prepare the migration of selected ZRC2 (Scilla) tokens to ERC20 (EVM). - Correct EVM gas-fee accounting. User do not need to take any action. Centralised exchanges may pause ZIL deposits and withdrawals and resume once hard-fork is rolled out successfully. Release details: https://github.com/Zilliqa/zq2/releases/tag/v0.22.1

Update on the recent security incidents Our investigation with an external cybersecurity firm is ongoing. Here’s what we can share today. Affected services and tokens X-Bridge and ZRC2 proxy contracts used by some liquidity pools, including PlunderSwap, have been affected. The affected tokens are zUSDT, SEED, kUSD and Zoge. Native ZIL and the Zilliqa EVM network are not affected. X-Bridge remains suspended. Please do not use X-Bridge or the affected liquidity pools until further notice. Security measures We are rotating all operational keys and working with exchanges and law enforcement. We will share further updates through our official channels. We will never DM you or ask for your seed phrase or private keys. Leadership Alexander Zahnd has stepped down as CEO at his own request. The Board has assumed direct oversight, supported by an external advisory firm specialising in cybersecurity and governance, until permanent leadership is appointed. Our focus remains on the security of user funds and full transparency throughout this process. We will also share the latest business developments with our strategic partners, LTIN and Telecom Liechtenstein.

Following the security incident involving the Zilliqa Ledger app, we worked with major exchanges to coordinate the migration of ZIL to Zilliqa EVM. This included South Korea’s five major exchanges: Upbit, Bithumb, Coinone, Gopax and Korbit. Throughout this process, we responded to the questionnaire and subsequent follow-up questions from the Digital Asset eXchange Alliance (DAXA), the self-regulatory organisation representing these exchanges. After several months of coordination, we are disappointed by Upbit and Bithumb’s decisions to delist ZIL. However, we appreciate that both exchanges are supporting ZIL withdrawals on Zilliqa EVM, allowing holders to move their funds without completing the migration manually. For holders on Upbit and Bithumb, there are two withdrawal options: - Withdraw to a self-custody wallet, such as MetaMask or Rabby. Add the Zilliqa EVM network using the official network details, then use your wallet’s Zilliqa EVM receiving address. - Withdraw to another exchange that supports Zilliqa EVM, such as Binance or KuCoin. Check that ZIL deposits are enabled and select the correct network before transferring. Please check each exchange’s official notices for withdrawal deadlines and instructions. Before transferring, confirm that your destination supports Zilliqa EVM and, if sending to another exchange, that ZIL deposits are enabled. If you experience any withdrawal issues, contact the support team of the exchange you are withdrawing from. Send a small test transfer first and confirm it has arrived before moving the rest of your ZIL balance.