Harmony ONE migration is currently a reported plan to sunset Harmony’s Layer 1 and move the ONE token to Ethereum; it is not the same as an automatic transfer already completed. The immediate priority for wallet holders is to verify official deadlines, claim instructions, and contract addresses before moving funds or signing anything.
The change matters because a self-custody wallet does not hold a balance independently of a blockchain. It displays what a network and its applications report for an address. If Harmony stops producing blocks, weakens support, or disables contracts, the private keys may remain safe while the practical ability to use, stake, swap, or migrate assets changes significantly.
What changed this week
On September 6, 2026, The Block reported that Harmony plans to fully sunset its Layer 1 and has proposed migrating ONE to Ethereum in connection with an AI video initiative. The report describes a planned transition, not proof that the network has already shut down or that every ONE holder has an active Ethereum claim.
That distinction is important. A news report can identify direction and intent, but only an official Harmony announcement, governance record, or published migration contract should define the final timetable, eligibility rules, conversion ratio, snapshot, claim window, and supported wallets. Until those details are published and independently verifiable, holders should treat unsolicited migration links as a security risk.
Harmony’s existing network is an independent Layer 1 with its own addresses, transactions, staking, and applications. Ethereum is a separate network with a different address environment and fee asset. A future Ethereum representation of ONE would therefore be a new token contract or migration asset on Ethereum, not merely the same entry appearing on a different network.
Why a network sunset affects self-custody
A seed phrase controls keys. It does not guarantee that a chain will continue operating, that a token contract will remain usable, or that an application will honor a balance after an upgrade. This is a central lesson of multi-chain custody: ownership and usability are related, but they are not identical.
If Harmony’s validators stop processing blocks, a wallet may still show a previously observed ONE balance. However, a new transaction could remain unconfirmed, a staking withdrawal could become difficult, and decentralized applications could stop responding. A wallet interface can also retain stale data if an explorer, RPC endpoint, or indexing service is no longer maintained.
A sunset can affect several types of holdings differently:
- Liquid ONE: The token may remain visible on Harmony even if markets, transfers, or bridges stop supporting it.
- Staked ONE: Delegated funds may depend on validator operations, unbonding rules, and a functioning chain after any announced deadline.
- Liquidity-pool positions: LP tokens, pool shares, or deposited assets may depend on smart contracts that cannot be migrated automatically.
- Lending and farming positions: A protocol may have separate rules for withdrawals, rewards, collateral, and liquidations.
- NFTs and other application assets: These can remain tied to Harmony contracts even if the main token moves to Ethereum.
- Bridged assets: A representation backed by a bridge may have risks involving the bridge operator, validator set, or redemption process.
The outcome for each category depends on the final technical plan. A token migration cannot automatically recreate every position in a DeFi protocol on Ethereum, because the destination application may not have equivalent contracts or liquidity.
What a migration could look like
A project moving a token from one chain to another commonly chooses one of several designs. The names vary, and the details of any Harmony plan must be confirmed from official documentation.
| Approach | What happens to the old asset | What the holder usually does | Main risk to check |
|---|---|---|---|
| Claim contract | The old token is locked, burned, or recorded | Connect a wallet and claim a destination token | Fake contracts, wrong deadline, or unsupported assets |
| Snapshot and airdrop | Eligibility is measured at a stated block or date | Wait for a distribution or claim | Holding the wrong asset type or missing the snapshot |
| Exchange-supported conversion | A platform handles the swap for customers | Deposit or opt in through that platform | Custody, jurisdiction, and platform support |
| Issuer-controlled replacement | A new Ethereum token is issued against a defined record | Follow issuer verification and claim steps | Centralization, unclear backing, or incomplete terms |
The key question is not simply whether ONE has an Ethereum token address. It is whether that address is the official destination asset, what backs it, who can claim it, and whether the old Harmony balance is burned, locked, frozen, or left circulating.
Ethereum also introduces transaction fees paid in ETH. A holder might need ETH on Ethereum to claim, transfer, or approve a replacement token. The amount and contract behavior should be visible before signing. Review Ethereum account and network basics if the difference between a Harmony address, an Ethereum address, and a token contract is unclear.
What happens to staking and validators?
Staking is especially sensitive to a Layer 1 sunset because it is part of the network’s security and consensus system. A delegated balance is not always immediately liquid: it may be subject to an unbonding period, validator status, slashing rules, or a separate withdrawal transaction.
Holders should look for explicit instructions covering:
- the last block or final staking date;
- whether delegations must be undelegated manually;
- the length of any unbonding period;
- whether rewards are included in a snapshot or claim;
- how inactive or jailed validators are handled; and
- whether staked ONE qualifies for an Ethereum migration.
Do not assume that a liquid ONE claim covers staked ONE. Staking records may live in a module or contract that a simple token snapshot cannot read. If an official process requires an unbonding transaction, allow enough time for it to complete before a stated cutoff, but rely on published network instructions rather than social-media countdowns.
What happens to DeFi and liquidity pools?
DeFi positions are application-specific. If ONE is deposited in a lending market, liquidity pool, vault, or farm, the wallet may not hold the underlying assets directly. It may hold a receipt token that represents a claim on a contract. A token migration by itself does not recreate that receipt on Ethereum.
Before any final deadline, holders should inventory positions and record:
- the protocol and contract address;
- the assets deposited and the amount shown by the protocol;
- any LP, receipt, or reward tokens;
- withdrawal, redemption, or unbonding requirements; and
- transaction history needed for accounting.
A protocol may publish its own migration, wind-down, or withdrawal process. If it does not, a user may need to withdraw while the contract and network remain functional. This is not a recommendation to rush into a transaction; it is a reminder that contracts can have different deadlines from the chain’s headline sunset date.
Do not approve a new token or connect to a migration site solely because it uses the word Harmony. Check the domain, contract source, official announcements, and transaction simulation where available. Never enter a seed phrase into a website, support form, or migration portal.
A safer checklist for ONE holders
Until final instructions are available, a measured approach is more useful than reacting to price or rumors:
- Locate every ONE balance. Check liquid, staked, bridged, exchange-held, and DeFi positions separately.
- Record the network. Note whether each asset is on Harmony, Ethereum, or another chain, and save contract addresses from trusted records.
- Back up your wallet. Confirm that your recovery method works without exposing the seed phrase. The keys remain important even if an application changes.
- Follow primary announcements. Prefer Harmony’s official channels and published technical documentation over forwarded links.
- Verify the destination token. Confirm the contract address, conversion mechanics, claim window, and whether the old token is burned or locked.
- Budget for Ethereum gas. A legitimate claim may require ETH, but do not send ETH to an individual or pay an unofficial activation fee.
- Test cautiously. If the official process supports it, use a small transaction first and confirm the destination asset in a wallet or block explorer.
- Keep records. Save balances, transaction hashes, claim confirmations, and dates for future reconciliation or tax reporting.
A wallet balance that disappears from one interface is not necessarily lost, and a new balance appearing on Ethereum is not necessarily an official migration. Compare the address, token contract, transaction status, and source of the information before drawing conclusions.
What wallet holders should watch next
The most consequential missing information is the implementation detail. Watch for a formal proposal or announcement that answers these questions:
Is the sunset approved and when does it happen?
A proposal, a governance vote, and an executed shutdown are different events. Look for the decision-making process, final block or halt date, validator instructions, and a communications channel that can be independently verified.
Who is eligible for the Ethereum claim?
The plan should explain whether eligibility is based on a snapshot, a live balance, a claim contract, or another record. It should also address custodial exchange balances, staked ONE, bridged tokens, liquidity providers, and contracts that cannot sign a claim directly.
What is the official contract?
A genuine migration should provide a precise, auditable destination contract and explain its permissions. Users should be able to compare the address across more than one official source and inspect the transaction before signing.
What happens to Harmony applications?
The main token can move while NFTs, DeFi positions, governance rights, and application data remain on the old chain. Each project may need its own plan, and some assets may not have an equivalent Ethereum version.
How long is the claim open?
A claim window, if one exists, should be explicit. A short deadline increases phishing risk because attackers can manufacture urgency. Never sacrifice verification for speed.
The practical takeaway
The September 6 report makes Harmony’s Layer 1 sunset and possible Ethereum migration the key development for ONE holders this week. For self-custody users, the event is less about simply adding an Ethereum token and more about mapping each position to its network, contract, staking state, and migration eligibility.
Keep control of your keys, preserve records, and wait for verifiable instructions before signing a migration transaction. If the plan becomes official, move only the assets covered by that plan and treat every other Harmony-based position as a separate technical question.
