CoinYQ Dossier

Zilliqa: the sharding pioneer that had to replace its own engine

Zilliqa turned a research idea into the first chapter of its identity. By 2026, the chain was running a new consensus engine and closing the old signing system after a costly failure. Its history is less a straight line of scaling than a sequence of engineering choices revised under real load.

A 2015 sharding paper became a public chain

Before ZIL had a market, the founders were trying to turn database sharding into a blockchain protocol. Early documents put Xinshu Dong in charge of the company, Yaoqi Jia over technology, Amrit Kumar over research and Prateek Saxena as scientific adviser. The team says the theory began in a 2015 paper; by June 2017 the effort had become Zilliqa, and its August whitepaper promised throughput that would grow as more miners joined.

Their design split the mining network into smaller groups that processed transactions in parallel. A Directory Service committee assigned nodes and assembled results, proof of work established identities, and practical Byzantine fault tolerance committed blocks. The wager was specific: parallelism would relieve congestion without making every node execute every transaction.

Scilla arrived just over four months after the chain

Mainnet opened on January 31, 2019, but it did not yet offer the complete application platform advertised during development. Smart contracts were activated on June 10. That gap matters because Zilliqa’s second invention was Scilla, a language that separates pure computation from the transitions that read state, write state and send messages.

The restriction was deliberate. By making effects explicit and limiting hard-to-analyse behavior, the language was meant to make contracts easier to reason about and formally verify. It could prevent some programming mistakes; it could not make applications infallible. Zilliqa had chosen a safer but unfamiliar language just as Ethereum’s Solidity tooling was becoming the default elsewhere.

The sharded pioneer temporarily removed its shards

Zilliqa added EVM compatibility in April 2023 so Solidity developers and MetaMask users could enter without adopting Scilla first. In the same year, low shard usage and faster block production created a different engineering problem. gZIL governance approved active reward control and temporary desharding ahead of the next architecture.

On December 18, incomplete microblocks reached only part of the network. Nodes calculated different root hashes, consensus lost enough votes to stop, and recovery code failed to activate; block production returned only after a restart. Version 9.3.0 arrived on January 3, 2024 with one shard. The chain famous for operational sharding had removed it to gain efficiency and reliability while its replacement was being built.

Zilliqa 2.0 replaced the engine, not the history

The 2024 redesign exchanged proof-of-work identity selection and PBFT for proof of stake and Pipelined Fast-HotStuff. It made EVM execution native, initially kept compatibility for migrated Scilla state, and proposed customizable x-shards rather than the old fixed shard layout. Aventurine imported historical state into a proto-mainnet in December 2024; the production migration occurred at block 4,770,088 on June 23, 2025.

Current RPC answers show the new chain running as chain ID 0x8001 with one shard. That is evidence of a live zq2 mainnet, not evidence that the proposed x-shard ecosystem is already deployed. The old balances and transaction history survived inside a new consensus system, while legacy staking users had to withdraw and delegate again through EVM contracts.

A wallet flaw forced the last legacy path to close

A defect present in every release of the Zilliqa Ledger app copied the wrong 32 bytes when creating Schnorr signatures. Eight zero-padding bytes remained and 64 bits of entropy disappeared. From four or more public signatures, an attacker could reconstruct a private key. Theft began on March 4, 2026 and went unnoticed until KuCoin reported anomalous withdrawals on July 19.

The proven loss was at least 683,130,969.66 ZIL; 6,772 accounts were known to be exposed and 51 were drained. Zilliqa disabled all legacy transaction functionality on July 20, preventing further use of that vulnerable path but also freezing innocent legacy holders. A September 2 hard fork moved the first ten exchange partners to EVM addresses. At review, the retail zero-knowledge migration tool and a second exchange batch were still pending, and a proposed compensation mint had not yet reached a published vote. The incident finished what the protocol migration had left open: the legacy execution path was being retired, not repaired.

How the project changed

  1. 2017-08-10
    The technical whitepaper turns sharding research into a protocol

    The team publishes version 0.1 after saying its sharding theory began in 2015 and the public project began in June 2017.

  2. 2019-01-31
    Zilliqa mainnet launches

    The sharded network enters production; smart-contract execution is still a later step.

  3. 2019-06-10
    Scilla contracts go live

    Developers can finally deploy the language designed to separate computation from state-changing communication.

  4. 2023-12-18
    Divergent root hashes stop block production

    Missing microblocks split node state; a failed recovery path makes a network restart necessary.

  5. 2024-01-03
    Version 9.3.0 deshards the network

    One shard replaces underused parallel shards while the team builds a different architecture for Zilliqa 2.0.

  6. 2025-06-23
    State migrates to Zilliqa 2.0

    At block 4,770,088 the network moves to the zq2 protocol, proof of stake and native EVM execution.

  7. 2026-07-20
    Legacy transaction functionality is disabled after proven theft

    A hard fork removes the vulnerable Schnorr path one day after KuCoin reports anomalous withdrawals; migration of frozen legacy balances continues afterward.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Zilliqa?

Zilliqa is a layer-1 blockchain whose native coin ZIL pays gas and secures the proof-of-stake network. Its first architecture used transaction sharding and Scilla; the 2025 Zilliqa 2.0 migration replaced the consensus engine, added native EVM execution and preserved legacy state.

What problem does Zilliqa solve?

The project began by asking how throughput could grow with the number of participating nodes. Years of operating the answer exposed harder questions: underused shards, restart-heavy upgrades, compatibility with mainstream tools and a legacy signing path that survived into the new chain.

How does Zilliqa work?

Zilliqa 2.0 validators stake ZIL and finalize blocks through Pipelined Fast-HotStuff. The June 2025 migration initially retained EVM and Scilla compatibility, but the July 2026 hard fork removed all legacy transaction functionality; the current destination is one EVM execution environment. Mainnet runs one shard, while configurable x-shards remain a separate expansion design. Frozen legacy balances must be reassigned or proven into EVM addresses.

Key facts

  • ZIL is the native gas and staking asset of Zilliqa; the BNB Smart Chain contract listed by aggregators is a wrapped representation, not the native coin.
  • The technical whitepaper version 0.1 is dated 2017-08-10 and describes network/transaction sharding coordinated by a Directory Service committee.
  • Early official documents name Xinshu Dong, Yaoqi Jia, Amrit Kumar and Prateek Saxena in leadership and research roles.
  • Mainnet launched on 2019-01-31; Scilla smart contracts were activated separately on 2019-06-10.
  • EVM compatibility reached mainnet on 2023-04-25.
  • After governance approved temporary desharding, v9.3.0 deployed on 2024-01-03 with one shard.
  • Zilliqa 2.0 migrated production state on 2025-06-23 with proof of stake, Pipelined Fast-HotStuff, native EVM execution and initially retained Scilla compatibility.
  • At review, RPC returned chain ID 0x8001, block 35,020,612, one shard with 81 peers and 20,569,524,088.609105613389 ZIL total supply.
  • The latest stable zq2 release found was v0.21.8, published 2026-08-21.
  • The Ledger post-mortem proves a floor of 683,130,969.66 ZIL stolen, with 6,772 accounts known to be exposed and 51 drained.
  • All legacy transaction functionality has been disabled since 2026-07-20; the first exchange-balance migration covered ten partners on 2026-09-02.
  • Retail migration, a second exchange batch and the compensation-tokenomics proposal were still future actions at review, not completed outcomes.

Official links

Categories

Related coins

Frequently asked questions

Does Zilliqa still use its original sharding system?

No. Governance approved temporary desharding and v9.3.0 moved the old network to one shard in January 2024. Zilliqa 2.0 proposes customizable x-shards, while current RPC still reports one live shard.

What changed in Zilliqa 2.0?

The June 2025 migration replaced the original PoW/PBFT arrangement with proof of stake and Pipelined Fast-HotStuff, made EVM execution native and initially preserved account state plus Scilla compatibility. After the July 2026 incident, all legacy transaction functionality was removed and migration now targets EVM addresses.

Why was Scilla created?

Scilla separates computation from state-changing communication so contract behavior is easier to analyse and formally verify. That design reduces some error classes but does not guarantee safe applications.

What happened in the 2026 Ledger incident?

The legacy Ledger app produced biased Schnorr nonces, allowing keys to be reconstructed from public signatures. The official floor is 683,130,969.66 ZIL stolen from 51 drained accounts.

Can legacy-wallet holders move ZIL now?

Legacy transactions are disabled. Ten exchange partners were migrated on September 2, but the self-guided retail migration tool was still planned for mid-September at review.

Will Zilliqa mint tokens to compensate victims?

The team said it was preparing a community vote, but had not published the amount, eligibility or final proposal. No compensation mint should be treated as approved yet.

External trackers

Choose a tracking site for Zilliqa: