ZetaChain's early pitch began with an everyday frustration: assets on different chains require different wallets, bridges and transaction sequences. Its August 2023 funding announcement said the project had started in 2021 and raised $27 million. Named participants included Blockchain.com, Human Capital, Vy Capital, Jane Street Capital and GSR. The proposed business was a common application environment for fragmented liquidity. Those backers document access to financing at that stage, rather than a standing guarantee of future funding or endorsement of every later product pivot.

The Mainnet Beta announcement published on February 2, 2024 described an operating network connected to Bitcoin, Ethereum and BNB Chain. ZetaHub combined staking, governance, applications and an activity rewards program in one entrance. Eligible users could claim an initial allocation, sometimes subject to identity checks. The launch therefore mixed infrastructure with a consumer onboarding campaign. Developers were offered a place to coordinate assets, while users were encouraged to explore it through a visible progression system rather than technical documentation alone.

ZetaChain's EVM documentation identifies a Cosmos SDK chain using CometBFT and Cosmos EVM. Solidity contracts and familiar Ethereum tooling run on its own ledger; the network is not an Ethereum rollup simply because its execution interface resembles Ethereum. The documented transaction formats include familiar EVM types, but blob transactions are unsupported. This combination lets a developer reuse contract expertise while relying on a different validator network and consensus system.

EVM compatibility describes an interface and execution model, not a transfer of Ethereum's security guarantees.

An account can appear as a zeta-prefixed bech32 address or as a hexadecimal EVM address when both derive from the same public key. The address guide demonstrates that these can expose the same balance, so moving funds between the two representations is unnecessary. It also points to a compatible account type when wallets disagree. This is a useful distinction for readers moving between Cosmos and Ethereum tools: an unfamiliar address format does not automatically mean that funds have crossed a bridge or entered another ledger.

The native token is ZETA, recorded in the smallest denomination azeta, with eighteen decimal places. It pays transaction fees and supports staking. WZETA is a contract representation created by locking native ZETA and issuing an equivalent ERC-20 compatible balance. Applications may need that wrapper because their interfaces expect tokens rather than a native coin. Separately, ZETA representations exist on connected EVM chains. These are different technical forms of the asset, so the network and contract identity matter more than the shared ticker.

The distribution document describes an initial 2.1 billion ZETA supply, with separate pools for user growth, ecosystem development, validators, liquidity, the treasury, contributors and purchasers or advisers. Locked tokens can participate in staking, which helps explain why circulating-supply figures may vary between services. Its longer-term model discussed inflation after roughly four years and allowed monetary-policy changes. That historical schedule should be read alongside subsequent governance rather than treated as a rule that cannot change with a restructuring of the network.

The 2025 whitepaper describes validators that observe external chains and jointly authorize transactions through threshold signatures. A Bitcoin transfer can lead to application activity on ZetaChain because that observation and signing machinery connects the two environments. Bitcoin miners do not thereby begin executing Solidity contracts. The paper's security argument depends on assumptions about the participating validator stake and signing process.

That distinction matters when interpreting the project's language about native access: remote assets remain subject to the actual custody and authorization arrangement connecting the chains.

The April 2025 threshold-BLS research post proposed a more flexible signing system while explaining why ECDSA would remain useful for chains such as Bitcoin and Ethereum. It discussed reducing coordination overhead and accommodating different cryptographic environments. This was a technical development direction, not evidence that every connected chain had switched signing schemes. Its broader lesson is that an interoperability system must satisfy the verification rules of each destination; choosing a signature scheme for one environment does not make it universally acceptable elsewhere.

The December 2024 Gateway announcement unified previously separate custody, connector and signing interfaces. A developer could deposit an asset, call an application, or request a withdrawal followed by a destination-chain call. ZRC-20 assets used a protocol-approved lock-and-release model, while the proposed Universal Token standard offered developers more control over token logic. The simplified interface removed steps from the user's screen, but the operation still involved multiple contracts and chains beneath it.

These mechanics explain the former service, not a promise of availability after its wind-down.

Core liquidity pools had a practical role in that architecture. The liquidity documentation explains that a Universal App needed the destination chain's gas asset to complete an outbound transaction. Pools pairing ZETA with representations of external gas tokens helped convert value for that expense. Arbitrage supported pool pricing, and liquidity incentives helped bootstrap the system. A displayed application action could therefore depend on sufficient pool liquidity as well as valid contract execution.

Transaction convenience and the underlying cost of remote execution were separate parts of the design.

The February 2025 Solana integration announcement described bringing Solana assets into ZetaChain's composable environment alongside Bitcoin liquidity. Its Gateway program used signature verification and replay protections suitable for Solana, while more extensive remote contract-call functionality remained under development in that account. This was interoperability between two running networks. It did not replace ZetaChain validators with Solana validators or turn native ZETA into a Solana token.

Those distinctions prevent the later migration proposal from being incorrectly backdated to the original integration.

The original growth effort also courted application builders. In September 2025, ZetaChain and Google Cloud's buildathon announcement highlighted projects including RunRealm, which linked running activity with game mechanics, and Xyra, a cross-chain lending project. Prize winners are evidence of what developers attempted and what the organizers chose to reward. They are not a census of recurring users or a security certification of the resulting applications. The event nevertheless shows that the ecosystem's ambition already extended beyond a simple bridge or a token transfer interface.

The staking guide describes rewards as transaction fees plus distributions from a funded emissions pool, allocated among validators according to voting power. It also states that the pool is manually funded and distinguishes those rewards from newly created inflation. This matters when interpreting staking returns: a token allocation can support validators before application fees alone cover the system's costs. The guide documents that economic mechanism, while actual reward rates and the remaining runway depend on the network's current parameters and funding decisions.

The Foundation's March 2025 delegation round selected smaller validators for support, beginning with an initial delegation and allowing subsequent increases after review. Eligibility included low voting power and business verification, with performance, governance participation and slashing history relevant to continued support. These were conditions of a sponsored delegation program, not proof that every validator needed Foundation permission to exist.

The program illustrates a recurring tension in new networks: distributing stake more widely can require a central organization to decide which independent operators receive help first.

ZetaHub's July 2024 loyalty design combined lifetime XP, named achievement tiers and active streaks. Applications could connect incentives to measured activity, while committees and application-specific campaigns shaped reward distribution. This turned participation into a recognizable routine: return, complete an activity and compare progress. The system also made a measurable score socially important.

Once contributors treated that score as recognition of their time, disagreements about thresholds became disagreements about who belonged, rather than merely complaints about a dashboard number.

In a thread opened in September 2024, ycr argued that years of articles, graphics, staking and personal expenditure were not adequately recognized by a proposed XP threshold. hcrawler replied that no metric would capture every genuine supporter, while vfragoso defended the higher cutoff as evidence of continued participation after mainnet. Their exchange preserves a specific disagreement between off-chain labor and measurable on-chain activity. None of these posts establishes how the whole community felt, but together they explain why reward rules became part of ZetaChain's community identity.

A community-tax proposal prompted a practical argument about who should pay for public development. Lucas worried that diverting rewards into a pool would reduce staking returns and suggested using an emissions allocation instead. Other participants emphasized grants, builders and a more active community. The disagreement was not simply support for or opposition to ZetaChain: it concerned which budget should finance shared work. It also exposed how readily a technical parameter can become a discussion of investor expectations and the obligations attached to holding a staking token.

A proposal to extend voting from twenty-four to seventy-two hours produced another clear division. denis favored time for consideration and discussion, whereas Slem argued that active members could vote within a day. The record contains suggestions for still longer periods as well. These are positions in a proposal discussion, not evidence that a particular duration was enacted. Separately, CharlieMc announced in March 2025 that the Discourse site would close and directed governance discussion to Discord; the surviving threads are historical records.

ZetaChain's postmortem says an attacker exploited arbitrary calls through GatewayEVM on April 26, 2026. Existing ERC-20 allowances let the gateway transfer tokens from wallets that had previously approved it. The team reported approximately $333,868 lost through nine drain transactions on four chains, affecting three team-controlled wallets, with no external user losses. It paused cross-chain transactions and described an immediate patch process.

These loss and victim classifications come from the project's report; they should not be expanded into a claim that the entire architecture was unaffected.

SolidityScan's technical analysis followed the authorization path rather than assuming the threshold signer itself had been stolen. A caller could request arbitrary execution, the relayer generated the corresponding destination action, and the gateway's checks did not reject the token-transfer selector. Previously granted allowances then supplied the spending permission. The important failure was composition: individually recognized contracts and signatures performed an action the wallet owner had not newly approved.

The published analysis provides transaction and code references for that account, rather than merely repeating a headline loss figure.

The official cross-chain wind-down notice set June 1, 2026 as the deposit cutoff and June 30 as the final withdrawal deadline. It said ZRC-20 withdrawals would then be paused indefinitely and external-chain observation terminated. This announced retirement concerned legacy cross-chain services as the team concentrated on private AI. It means the earlier Gateway, pool and Solana-integration documentation belongs to the network's history, rather than serving as reliable instructions to initiate a new transfer. The notice is a publisher status record, not an independent test of every endpoint.

In September, the team reported 99.4% approval for moving native ZETA and its application layer to Solana. The announcement retained one-to-one conversion, unchanged supply and vesting, and excluded Ethereum and BSC representations. It gave no migration date. Exchanges and a further proposal would define execution; the L1 would continue until holders moved. The team's report establishes approval of a direction, not completed migration.

Anuma's September 29 announcement presented Nearby, a New York launch using AI context to suggest people to meet. The publisher described opt-in discovery, encrypted user-controlled memory and ZETA locking in exchange for AI credits. These are the company's product and privacy claims, not an independent audit of its data handling. They nevertheless show the concrete change in the token's proposed utility: access to an AI application layer rather than primarily paying a universal ledger to move assets between networks.

Earlier contributors had already debated whether community loyalty should be transactional. In a September 2024 advocacy discussion, dimka1109 said participants expected rewards despite the absence of a promise. DAOist_JC explicitly rejected that assumption and invited ideas for continuing contribution beyond airdrop seasons. Suggestions included regional participation and application-linked NFTs. That historical disagreement gives context to later product changes without claiming the same people approved them.

A community formed around testing bridges and collecting XP need not automatically share the team's next commercial ambition.