The Zilliqa hard fork on September 2, 2026 successfully migrated balances to new addresses at the protocol level, but exchanges must complete their own internal testing before reopening deposits and withdrawals. Three days after the fork, major trading venues including Bitvavo, WhiteBit, and KuCoin still had ZIL transfers disabled, even though trading remained active on some platforms.

What Actually Happened During the Zilliqa Hard Fork?

On September 2, 2026 at approximately 12:58 UTC, the Zilliqa blockchain activated a hard fork at block height 34,844,968. This was a protocol-level rule change that automatically reassigned ZIL balances from legacy addresses, which use Schnorr signatures, to new Zilliqa EVM (Ethereum Virtual Machine) addresses that follow the Ethereum address format. By September 5, the blockchain had progressed over 200,000 blocks past the fork height, confirming the protocol change was fully active and irreversible.

The fork targeted ten exchange partners in its first phase: KuCoin, Binance.US, MEXC, OKCoin, Bitvavo, Korbit, WhiteBit, Bitrue, CoinSpot, and CoinSwitch. However, the protocol's work ended once balances were reassigned. What happens next depends entirely on each exchange's internal systems and timeline.

Why Can't You Withdraw Your ZIL Yet?

This is where the disconnect between protocol and platform becomes critical. A blockchain hard fork can move balances automatically, but it cannot force an exchange to reopen its withdrawal systems. Each exchange manages a pooled balance for all its customers in its own wallets. When the underlying address format changes, the venue must migrate its entire internal allocation system, test it thoroughly, and reconcile every customer account balance before allowing transfers out again.

If something goes wrong during this process, the exchange, not the protocol, bears the liability. That's why Zilliqa's official announcement contained no reopening date, only a reference to venues conducting their own testing. On September 5, 2026, a direct query of three participating exchanges revealed the reality on the ground:

• Bitvavo: Already displays ZIL on the ZILEVM network but shows both deposits and withdrawals as "MAINTENANCE," while trading continues normally.
• WhiteBit: Reports both deposits and withdrawals as disabled and still lists the old ZIL network, not the new ZILEVM network.
• KuCoin: Shows ZIL chain deposits and withdrawals as switched off entirely.

This snapshot from September 5 reveals that three days after the fork, none of the three venues checked had released transfers, and two still carried ZIL under the old network label.

How to Monitor Your Exchange's Migration Status

• Check the Network Label: If your exchange shows "ZILEVM" as the network, the balance reassignment has arrived and only the transfer release is pending. If it still shows "ZIL," your provider is earlier in the migration process.
• Look for Status Indicators: In most exchange apps, deposit and withdrawal status appears next to the withdrawal button or on the provider's dedicated status page. "MAINTENANCE" means testing is underway.
• Verify Trading Availability: An exchange can keep trading active while transfers are frozen, so the ability to sell your ZIL does not mean you can move it to another platform.
• Document Your Timeline: If withdrawals remain frozen for an extended period without updates, take screenshots of your account balance and the frozen status for your records.

What About Self-Custody Holders?

If you hold ZIL in your own wallet rather than on an exchange, the September 2 hard fork did not affect you at all. Self-custodians were not part of the migration process because they control their own private keys and addresses. Their balances remain on the legacy address format unless they manually interact with the new network, which requires deliberate action on their part.

When Will the Next Wave of Exchanges Migrate?

Zilliqa announced a second hard fork scheduled for "mid-September" to migrate the next group of trading venues. However, this timeline carries no firm date. The protocol team stated that address mappings for additional partners were still being collected and checked, and the exact date would be confirmed once those mappings were settled. Anyone holding ZIL at an exchange not included in the September 2 group has not been forgotten, but their migration remains pending an announcement that has not yet arrived.

The key takeaway is straightforward: the blockchain did its job on September 2. Now it's waiting on the exchanges. Only your provider can answer when you'll be able to move your ZIL again, and that answer depends on how quickly they complete their internal testing and reconciliation. Until then, trading may continue, but transfers remain frozen.