ZETA's proposed 1:1 Solana move: what holders need to check before December

A token balance and a transfer route are different questions

The proposed ratio preserves token units: one eligible native ZETA would correspond to one ZETA on Solana. It does not set a dollar redemption value. A holder deciding whether to transfer should therefore ask which chain the receiving service supports, rather than infer that the unchanged ticker makes every destination interchangeable.

The project's explainer says the ZetaChain L1 would stop at the snapshot height and would not restart. It also says ZETA on Ethereum, the ERC-20 version, is unchanged by this proposal. Those two statements make the network distinction material: the retirement of one chain should not be described as every existing ZETA representation disappearing. Project holder guidance.

Start with a record of the balance location and asset network. If the tokens are on an exchange, examine that exchange's own ZETA notice and deposit or withdrawal screen before initiating a transfer. If they are in a wallet, determine whether the wallet directly controls native ZETA, an Ethereum token, a wrapped position or a pool receipt. The project gives different instructions for these holdings.

Our funding board and liquidation board answer market-position questions. They cannot establish whether a particular account has completed a token conversion. A price quote, an exchange account balance and a successful on-chain claim should be checked separately.

What the second proposal actually changes

The November 4 explainer identifies this as the second migration proposal and links to proposal 70 on ZetaHub. It says the earlier proposal approved the direction, while the new vote sets the mechanism, dates and holder protections. If the vote fails, the project says it would return with revised terms; nothing moves on the present terms. ZetaChain proposal explainer.

Under the proposed sequence, every native ZETA balance is captured at a published block height. The categories listed include liquid holdings, staked tokens, unbonding positions and unclaimed rewards. The L1 stops at the same height. The corresponding supply is minted on Solana before the claims portal opens, after which mint authority is revoked, according to the project.

This sequencing matters to someone checking a balance after the proposed shutdown. The project says claims use the published snapshot rather than the live chain. Its description therefore makes the snapshot record the reference for entitlement. A holder should retain the wallet address and balance records needed to compare the published allocation with the position actually held.

The post also says the Solana token would have nine decimals and no freeze authority. These are proposed token settings, not findings from an independently inspected deployed mint. The project says it will publish the mint address and migration-program address before December 9. Those addresses are a specific piece of evidence to wait for before treating an unsolicited token as the replacement.

Exchange users: check the venue's own conversion window

ZetaChain says exchange balances would convert automatically, without holder action. In the same FAQ it says each exchange announces its own conversion window. The project-level statement is therefore not an exchange-specific timetable, and this article does not establish that any named venue has already accepted the terms. Exchange-balance FAQ.

For an exchange-held position, look for a notice that names ZETA and distinguishes trading from deposits, withdrawals and conversion. Read the applicable network and the venue's stated window together. If no matching notice is available in the account, keep that absence as an unresolved operational question; do not substitute the project's target date for the venue's instructions.

A pending withdrawal needs its own record: the selected network, destination and transaction status. Before making a second transfer, reconcile the first transfer with the account history. This is a practical check arising from the proposed network change, rather than a report that withdrawals are currently suspended or that any venue has lost balances.

The conversion ratio also does not describe an open derivatives contract. A reader holding a ZETA trading position should read the specific instrument's terms and any venue notice. Nothing in the project blog proves how a particular perpetual contract, margin position or open order would be handled.

Wallet users: distinguish a signature from a transaction

The project's proposed process is to connect the wallet that held ZETA, sign a message naming a Solana destination wallet and receive the full eligible balance. It says the migration requires no fee or SOL and never asks for a seed phrase. It identifies ZetaHub as the portal and states a minimum of 10 ZETA at the snapshot for claiming. Wallet-claim instructions.

Those instructions describe a future process. They do not create a reason to use a claim page sent by direct message today. The official post says most holders need do nothing until December 9, and that the portal and its program are undergoing independent review by Hacken. It says the review must finish and the report must be published before the portal opens.

For a directly controlled wallet, save the official explainer and return through the project domain when the published process is available. Compare the signing request with the action described there. A request for a seed phrase or a payment conflicts with the procedure the project currently describes; stop that request and check the official instructions.

Staked and unbonding holders have a different immediate question. The project says both positions, plus unclaimed rewards, are credited at the snapshot and holders need not unstake. Staking rewards would stop at that height. A decision to unstake solely because of a migration headline would therefore overlook the treatment set out in the proposal.

Wrapped tokens, pools and other bridged assets need separate attention

The project's FAQ tells holders of wrapped or pooled ZETA to unwrap and exit pools before the snapshot. Its stated reason is that tokens inside contracts and pools cannot be claimed by a key. A pool position should therefore not be assumed to receive the same direct-wallet treatment merely because a portfolio interface labels its value in ZETA. Wrapped and pooled holdings FAQ.

The useful check is the actual position: identify the contract or pool holding the tokens, the route for withdrawing and the output asset. Check the live position before submitting an exit. This article supplies no current liquidity quote or transaction simulation, so the proposal's general instruction should not be read as a verified execution price for a particular pool.

Assets bridged into ZetaChain are another category. The post says assets still held as ZRC-20 tokens at the snapshot could be claimed back on their original chains from December 9, with a minimum of $5 per token. That is a separate claim from receiving Solana ZETA and should have its own asset-and-network record.

Keep the two tasks distinct when reviewing a wallet: claiming ZETA concerns the replacement token, while recovering a connected-chain asset concerns that asset's original chain. Using the same date for both processes does not make their destination networks or asset identifiers identical.

The burn plan is a schedule, not a return calculation

The project timeline describes twelve monthly burns of about 4.6 million ZETA during 2027, following the schedule on which undistributed validator emissions would otherwise have been released. This is the timeline wording; the earlier supply paragraph uses a different, ambiguous description of the amount. Project supply schedule.

The rounded monthly figure should not be multiplied into a supposedly exact total. For a holder checking implementation, a dated burn transaction and the supply record would be more useful than treating the rounded headline as a completed reduction today.

The post says purchaser and core-contributor vesting completes on January 1, 2027. It also describes a commitment concerning sales of newly released tokens. An unlock date, a stated sales commitment and a completed sale are different observations. None supplies a basis for predicting the token's market price.

ZetaLabs, the proposed private AI application, is scheduled to launch alongside the migration. That product plan explains the project's intended role for ZETA, but a launch timetable is not a measure of adoption or token demand. The holder decision examined here remains whether the custody and claim path is correctly identified.

What to watch before treating the migration as complete

The next concrete item is the vote outcome. After that, the project's own checklist names the security-review report, the SPL mint address and the migration-program address before the proposed December date. Exchange users additionally need their venue's conversion notice; wallet users need the published snapshot and applicable claim instructions.

At this run's review, the opened sources establish a proposal and a target calendar, not a completed migration, final audit report or current exchange-wide support list. Keep records of the relevant wallet or account position and compare them with those later documents. The published funding board remains a separate market tool; it cannot answer whether a wallet has received its allocation.

Quick answers

Is the migration complete?

No. The opened project post makes implementation conditional on the second proposal passing. Its calendar lists the vote closing before the proposed December migration.

Does 1:1 protect the dollar value?

The proposal specifies a token-unit conversion. It does not establish a fixed dollar redemption price.

Do staked holders need to unstake?

The project says staked and unbonding balances, plus unclaimed rewards, are credited at the snapshot without unstaking. The proposed snapshot is also when staking rewards stop.