Harmony's Sunset Proposal Was Not a Completed Migration
Harmony governance separates proposals, validator voting and implementation into distinct procedural steps.
Prepared automatically from the linked sources. The category byline does not confirm personal authorship or review. Editorial policy.
A proposed endpoint
In its September report, Cointelegraph described Harmony’s proposed shutdown of its blockchain and migration of ONE to Ethereum. The plan envisaged a final network snapshot, replacement tokens and changes to exchange listings. Crucially, the report described the proposal as nonbinding. It did not identify a final block date or establish whether the shutdown would enter validator governance. Cointelegraph
The report also distinguished what would move. The reported snapshot would include wallet balances, staking delegations and validator rewards, but multisignature safes, liquidity pools and onchain applications could not migrate. Editorial analysis: a balance record and a functioning application are different deliverables. At that reported stage, a proposed snapshot described an intended accounting boundary; it was not evidence that replacement tokens had been issued or that applications were operating elsewhere. Cointelegraph
Decision and implementation
Harmony’s governance documentation describes proposal, voting and implementation as parts of its network model. Elected validators can submit proposals, including a summary and a link for forum discussion. Unelected validators can also vote. Voting power follows the amount of ONE staked with a validator, so participation is tied to delegated stake rather than a simple count of people expressing support. Harmony governance
The documentation distinguishes an introductory period from voting and specifies participation and approval requirements. It also explains that delegation changes can affect voting power before the closing snapshot. Editorial analysis: these rules explain how a decision can be recorded; they do not themselves record a particular decision. A discussion post, an eligible proposal, a successful vote and implementation answer separate questions. Reading the procedure cannot substitute for evidence of those individual steps. Harmony governance
Token interface and delivery
The Ethereum token standard defines an interface for tokens implemented through smart contracts. It covers balances, transfers and permission for another party to spend tokens. Standard interfaces allow applications, including wallets and decentralized exchanges, to reuse token functionality. Transfers and successful spending approvals also have specified events. Ethereum standard
Editorial analysis: describing a proposed asset as ERC-20 identifies the intended interface. The standard is a specification for contract behaviour, not a certificate that a particular contract has been deployed or a distribution completed. Its functions describe what compliant token interactions look like. They do not document the reconstruction of another blockchain’s applications, the completion of an exchange migration or delivery to every intended recipient. Those are implementation claims requiring their own evidence. Ethereum standard
An address is not deployment
Ethereum’s account documentation distinguishes an account from a wallet: a wallet is an interface or application used to interact with accounts. Accounts may be controlled by users or smart contracts. A contract receives an address when deployed, while one documented deployment method also allows an address to be calculated before the contract exists. An address and a deployed contract therefore need careful distinction. Ethereum accounts
Editorial analysis: seeing a familiar address in a wallet interface is not, by itself, proof of a deployed application. The documentation’s distinction between an interface and an account explains why the visible identifier cannot answer every technical question. Where a contract address can be known in advance, its appearance is especially limited evidence: identifying the destination and demonstrating that executable contract code exists there are different observations. Ethereum accounts