Your ZIL sits on an exchange, the hard fork of September 2, 2026 has gone through, and you still cannot withdraw anything. This is not a fault in your account and not a sign that something ha
Your ZIL sits on an exchange, the hard fork of September 2, 2026 has gone through, and you still cannot withdraw anything. This is not a fault in your account and not a sign that something has been lost: the hard fork was the protocol's step, reopening deposits and withdrawals is your exchange's step. The two do not happen on the same day.
On September 5, 2026, three days after the fork, we queried the public interfaces of three of the ten trading venues involved. At all three, ZIL deposits and withdrawals were halted at that point. At one of the three, trading was running normally at the same time. This article tells you why that is, what you can do right now, what you are better off avoiding, and what you are waiting for if you hold your ZIL in self-custody.
A hard fork is a rule change in a blockchain's protocol that every node has to adopt, because only the new rule applies afterwards. The Zilliqa hard fork of September 2 did one single thing: it moved the ZIL balances of a first group of ten exchange partners from their old legacy addresses to their Zilliqa EVM addresses. Zilliqa describes this step as a protocol-level reassignment that required no action from users.
That puts the exchange's balance in the right place. What comes next, however, is no longer up to the protocol. In its own blog post of September 2, Zilliqa writes verbatim that exchanges are working through their own testing before they restore ZIL deposits and withdrawals on their platforms. In plain terms: the trading venue has to move its wallet system, its address management and its bookkeeping over to the new side of the chain and verify all of it. How long that takes is its own decision, and none of the ten exchanges has committed to a date.
For you as a holder, that leaves an uncomfortable but clear position. You can wait, and, provided your exchange keeps trading open, you can sell. What you cannot do is move your ZIL out. Anyone who would rather hold their balance on a different platform cannot get it there during this phase. An overview of the providers is still worth having, because after an incident like this the question of who you trust with your holdings comes up again (our overview: crypto exchanges compared).
The fork was tied to a block height, not to a clock time: block 34,844,968, activated on September 2, 2026 at around 12:58 UTC. That number is the only hard marker in the whole process, and it can be checked independently. On September 5, 2026 at 06:37 UTC, the public Zilliqa node reported 35,045,411 transaction blocks. The chain is therefore a good 200,000 blocks past the fork height: the fork is unambiguously active, and anyone still waiting for it to activate is waiting for something that happened long ago.
According to the announcement, ten trading venues were affected: KuCoin, Binance.US, MEXC, OKCoin, Bitvavo, Korbit, WhiteBit, Bitrue, CoinSpot and CoinSwitch. In its blog post Zilliqa itself speaks only of a first group of ten exchange partners and does not name them there; the list comes from the announcement published in advance, which we analysed on August 29, 2026 in our overview of the Zilliqa hard fork and the ZIL migration. If your holdings sit with a different provider, you were not part of that day, and there is a reason for it further down.
Rather than rely on announcements, on September 5, 2026 between 06:36 and 06:37 UTC we queried the public interfaces of three of the participating venues ourselves. The result is unambiguous and unwelcome for investors:
This measurement is a snapshot, not a permanent state. What it does reveal, though, is something that appears in no announcement: three days after the fork, none of the three venues checked had released transfers again, and two of them still carried ZIL under the old network label. So check the status at your own provider instead of relying on reports about others. In the app it usually sits right next to the withdrawal button, otherwise on the provider's status page.
Zilliqa has two address formats, and the entire process turns on the switch between them. A legacy address is the network's old address form, secured by Schnorr signatures; a Zilliqa EVM address is the new form, which follows the address format of the Ethereum Virtual Machine and therefore works with common wallets. The hard fork rewrote balances from the first form to the second.
For you, the network label is therefore a usable status indicator. If your provider already shows ZILEVM as the network, the reassignment has arrived there and only the transfer release is missing. If it still shows ZIL, the provider is not that far along with its migration. In practice both mean the same thing for you: wait. The difference lies in how far your provider has already got.
The second case matters and is often overlooked. Anyone holding ZIL not at an exchange but in their own wallet was not affected by the September 2 fork at all. For self-custodians, nothing changed that day. What happens to that group is covered further down.
This is the point at which most readers misread the process. A protocol can move balances; it cannot force an exchange to open its withdrawals. An exchange manages a pooled balance for its customers in its own wallets. If the address format underneath that balance changes, the venue has to bring its entire internal allocation across, test it and reconcile it against account balances before it lets money out again. If something goes wrong in the process, the exchange is liable, not the protocol.
That is exactly why Zilliqa's own text carries no date for the reopening, only the reference to the venues' ongoing testing. Anyone expecting Zilliqa to answer the question of when they can withdraw again is asking in the wrong place. Only your provider has that answer.
You may know the pattern from other cases: the balance is visible in the account but cannot be moved, and support names no date. We have described how to proceed sensibly in such situations and what you should document in a separate guide (crypto exchange: account frozen, what to do).
In its blog post of September 2, Zilliqa announced a second hard fork intended to migrate the next group of trading venues. The timing is given, verbatim, as "mid-September". The address mappings of further partners were still being collected and checked, and Zilliqa would confirm the exchanges and the exact date once those mappings were settled.
Take that statement for what it is: a declaration of intent without a deadline. "Mid-September" is not a date on which you could do or check anything. Anyone turning it into a specific day is inventing it. The only reliable part of the statement is its direction, and for those affected at providers left out so far that is at least good news. On this point Zilliqa writes verbatim that anyone holding ZIL at an exchange not covered on September 2 has not been forgotten: that exchange's submission is still being processed.
In practice that means: if your provider was not in the group of ten, your current situation is unchanged, and the next marker is an announcement that is still outstanding. Calendar entries for an invented date do not help. A look at your provider's status page every few days does.
Zilliqa says the tool for self-custodians is in its final development phase and slated for mid-September; the project has not yet named a launch day. Self-custody means that you hold your coins in your own wallet and control the private key yourself instead of leaving it with a provider. In the Zilliqa incident this is the larger group, and it is waiting the longest. Zilliqa concedes as much in the blog post and describes it as the group that has been hardest to keep waiting.
The state of play according to Zilliqa: the self-service migration tool is in its final development phase and on track for a release in mid-September. It is to be built on zero-knowledge proofs. A zero-knowledge proof is a cryptographic proof with which you can demonstrate that you know or own something without disclosing the thing itself. For the migration that means, concretely: you should be able to move your stuck legacy balance to a Zilliqa EVM address yourself, without showing anyone your seed phrase or your private key, neither Zilliqa nor anybody else.
The most important warning in this text follows from that design. The real tool will never need your key. Every site, every form and every direct message that asks you during this waiting period for a seed phrase, a private key or a wallet approval in order to "migrate your ZIL" is therefore, by the project's own blueprint, not the announced tool. And as long as Zilliqa has published neither a start date nor an address, there is nothing you would have to unlock in advance. If you want to be safe, keep larger holdings on a device that does not release the private key in the first place, and do not type it in anywhere.
A trusted setup is the launch procedure of a zero-knowledge system in which several participants jointly generate secret starting values and then destroy their respective shares. The purpose: as long as even one participant honestly deletes their share, nobody can produce forged proofs later. Whoever held all the shares could evidence balances out of nothing.
Zilliqa writes that it is currently settling the circle of participants for this ceremony, and names as already confirmed the company itself, LTIN, an independent Web3 security audit, an exchange partner and participants from the community. The full list and the details of the ceremony are to be published before the tool launches. Zilliqa states the principle behind it explicitly: no single party should be able to act alone on a matter this sensitive.
For you this is not a technical detail at the margin but the question to ask before first use. If the tool appears without that list having been published beforehand, the whole thing is missing precisely the part that makes it verifiable. In that case it is worth waiting a few days rather than being the first to migrate.
The question that occupies those affected most is the one about the money that drained away in the incident. Zilliqa answers it in the blog post of September 2 in two parts, and both parts belong on the same line, otherwise the picture comes out skewed.
First, the legal route. Zilliqa describes the legal recovery of stolen assets through cross-border tracing and enforcement as a real path, but at the same time as a slow and uncertain one; anyone claiming otherwise about such proceedings is not being honest. That candour is unusual and, for you as a reader, the more useful information: no money will come from that route for the foreseeable future.
Second, the vote. In parallel, by its own account, Zilliqa is preparing a community vote on an adjustment to the tokenomics that would include re-minting tokens to compensate those harmed. The term tokenomics describes the rules by which a cryptocurrency is issued, distributed and capped. Zilliqa explicitly explains why this is not decided alone: the step changes the total supply and therefore affects every ZIL holder, not only those directly harmed. Mechanics, size and eligibility are to appear in the full proposal on the project's governance portal.
We queried that portal on September 5, 2026. The most recent post published there dates from April 10, 2026; a compensation proposal was not among the entries at that point. So there is currently nothing you could vote on and no text whose terms you could examine. Anyone telling you otherwise knows a source that does not exist.
Re-minting creates additional tokens that did not exist before. No existing holdings are redistributed in the process; the total supply grows. Every individual holder's share of the total therefore falls without the number of their tokens changing. The technical term for this effect is dilution.
The proposal thus has two sides, and an honest text names both. For those harmed it would be the faster route to compensation, probably considerably faster than any court proceedings; Zilliqa argues along those lines itself. For all other holders it is a burden they carry without having been harmed themselves. Zilliqa explicitly puts this trade-off to the community to decide rather than deciding it: the wording in the blog post is that it wants to give the community a genuine choice between speed and other trade-offs.
If you hold ZIL and this proposal appears, that is the moment when you have something to decide yourself. Until then the position is: there is no resolution, no promised sum and no defined group of eligible claimants. There is the announcement that there is to be a proposal.
Compensation from newly minted tokens shifts weight: what those harmed would receive is carried by all remaining holders through dilution. For the day on which transfers are switched back on, the terms are worth a look, particularly with a cryptocurrency at a very low unit price, where fees are stated in units rather than as a percentage. The values we read from the public interfaces on September 5, 2026 show the order of magnitude:
These figures change as soon as a provider resumes operations, and they are not a recommendation for or against any venue. The point behind them is a different one: with small holdings the fee can account for a noticeable part of the balance, and a balance below the minimum amount cannot be withdrawn at all. Anyone in that position is choosing between leaving it where it is and selling, not between withdrawing and waiting. Look at your own provider's terms on the day of the release instead of relying on older figures.
The Zilliqa case demonstrates a property that otherwise stays in the background: anyone holding coins at a trading venue holds a claim against that provider and not the coin itself. As long as everything is running, the difference is invisible. It becomes visible the moment the protocol changes something and the provider has to follow.
The reverse conclusion does not hold, however. On Zilliqa's account, the whole process was triggered by a signature bug in the Zilliqa application for Ledger devices, that is, in the self-custody area of all places. In this case those who self-custody are waiting even longer than the customers of the ten exchanges, because their tool does not yet exist. The more useful lesson is therefore that anyone who knows both routes and deliberately splits their holdings has more room to manoeuvre in phases like this than someone who keeps everything in one place.
The primary sources for this article: Zilliqa's status report of September 2, 2026 and the project's governance portal, on which the compensation proposal is to appear.
(As of September 5, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)
