Other system
Harmony ticker ONE
Historical network. Its profile describes the design as history. The evidence is in the system note below.
Summary
Until 10 September 2026 Harmony ran its own proof-of-stake chain split into two shards: shard 0, which also served as the beacon chain, and shard 1 (there were four shards until November 2023). ONE holders staked or delegated to validators. At the end of each 32,768-block epoch (about 18 hours) an election assigned voting slots, holding each key's effective stake between 85% and 115% of the median. On each shard a leader proposed a block about every 2 seconds and validators signed it with aggregated BLS signatures in a PBFT-style protocol Harmony calls FBFT; a block committed once signatures from more than two thirds of voting power were collected. Shard blocks were cross-linked into the beacon chain. After an exploit in August 2026 the chain was rolled back, and it stopped producing blocks at the September 2026 migration cutoff. 1231213141516
Design
- System
- Other systemHarmony no longer runs as a chain. It was a permissionless, sharded proof-of-stake layer 1 with an Ethereum-compatible virtual machine (shard 0 EVM chain ID 1666600000). Harmony announced on 6 September 2026 that it would retire the chain, citing threats from state-backed attackers and AI agents; the last shard-0 block came at 14:41:43 UTC on 10 September 2026, just after the migration snapshot. ONE balances are to move to a fixed-supply ONE token on Ethereum, an ordinary token rather than a layer 2. As a halted chain it is described here as history, not as a live layer 1.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- One leader per shard per round, rotating among elected validator keys since October 2024, with a view change replacing a failed leader. In the final epoch (3030) 43 validators were elected: shard 0 had 196 voting slots from 27 validator accounts and shard 1 had 204 slots from 32 accounts. Harmony's own nodes held 2 slots per shard with 1% of voting power. On each shard the five largest accounts together held more than a third of voting power. No leader has produced a block since 10 September 2026.
- Fork choice
- No open weight-based fork choice: a block committed once more than two thirds of voting power had signed it, and shards followed the beacon chain for committee elections. In August 2026 Harmony developers and validators discarded every block after shard 0 height 92,730,034 and shard 1 height 94,978,278 and restarted from those checkpoints, with node software that rejects the abandoned blocks by hash. The final state is fixed because no new blocks are produced.
Qualifications
- Live chain status · Not applicable. On 27 September 2026 Harmony's own RPC endpoints, two third-party RPC providers and the Harmony explorer all reported the same last shard-0 block, 93,624,315 at 14:41:43 UTC on 10 September 2026, and shard 1 stopped 11 minutes later. Block time, fees, validator counts and node requirements in this profile describe how the chain ran.
- Finality · Contested. In normal operation a block was final once more than two thirds of voting power signed it, with no ordinary reorganizations, and Harmony's docs say keys caught signing conflicting blocks were slashed (at least 2% of the stake behind them, validator and delegators alike) and banned. In August 2026 validators nonetheless abandoned committed blocks after shard 0 height 92,730,034 and restarted from a team-published clean database, so finality in practice depended on coordinated operator action. Harmony's own count, as reported by crypto.news, was 141,628 discarded shard-0 blocks.
- Sharding · Partial. Harmony split accounts and execution across shards inside one protocol: four shards until the HIP-30 hard fork of November 2023, then two. Shard 1 was part of Harmony itself, not a layer 2 or sidechain, which is why no scaling layer is listed.
- Settlement family · Partial. Harmony ran the Ethereum virtual machine and accepted 0x addresses and Ethereum wallets, but it had its own consensus and never settled to Ethereum. Only the replacement token planned by the migration lives on Ethereum.
- Throughput · Not applicable. Harmony's docs describe 2-second blocks and fast consensus but give no classed transaction-rate figure, and the chain no longer processes transactions, so no throughput claim is recorded.
- Migration status · Unknown. The migration repository says its source package is ready for independent review but is not itself a distribution file, and totals are withheld. The Ethereum address of the new ONE token and whether any distribution has started were not verified.
- Official shutdown notice · Partial. Harmony announced the shutdown plan on its X account on 6 September 2026, as The Block and crypto.news reported; the post itself could not be read for this review. No shutdown or migration notice appears on harmony.one, docs.harmony.one or the Harmony blog, whose latest post is from May 2026, and the harmony.one homepage now presents an AI video product.
Tradeoffs
- Emphasizes
- Scalability and Security
- Gives up
- Broad participation and continuity. Sharding and 2-second blocks came with a small elected validator set in practice (43 elected validators, and five accounts above a third of voting power on each shard at the end), full nodes that needed several terabytes of traffic a month, and security failures answered by developer-coordinated intervention: a recovery fund after the 2022 bridge theft, a rollback after an exploit in August 2026, and finally a snapshot-and-migrate plan that ended the chain in September 2026.Security is listed because Harmony's docs describe random, reshuffled assignment of validators to shards as the defence against taking over a single shard, and because blocks needed two thirds of voting power. The node repository still lists resharding as planned rather than done, and the August 2026 rollback shows that committed blocks could still be reversed by coordinated operators. The emphasis describes the design goals, not the outcome.
- Full node at home
- Not applicable 41618There is no live network to follow: shard 0 has produced no block since 14:41:43 UTC on 10 September 2026. While it ran, Harmony listed for a shard-0 validator 8 dedicated cores, 8 GB of RAM, a 1 TB SSD using Harmony's snapshot database (NVMe recommended), 50 Mb/s of bandwidth and 5 to 6 TB of data per month. A shard-0 RPC or explorer node needed a 6 TB SSD and a shard-0 archive node 32 to 36 TB; shard 1 needed far less storage and computing power but the same bandwidth.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Not present | None: shard 0 has produced no block since 10 September 2026, so no swap can settle on Harmony. While the chain ran, only building blocks were recorded: EVM contracts could have implemented hash time-locked swaps, but no protocol-level swap mechanism or deployed swap tool was verified. 16 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Not present | None: shard 0 has produced no block since 10 September 2026, so there is no new state to verify, and no user-facing light client for Harmony was verified while it ran. Cross-links let the beacon chain record shard blocks, which is internal bookkeeping rather than light verification for users. 316 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown. The earlier review found no payment or state channel layer anchored to Harmony, and none can operate on a halted chain. |
| Programmable spending | None found Earlier definition | Nothing can execute since the halt. While the chain ran, spend conditions were EVM smart contracts, including multisig and smart-contract wallets such as 1wallet, alongside separate staking transaction types. The migration does not carry contract code over; reviewed multisig and 1wallet balances are handled in a later stage. 111620 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Not present | None: no mechanism for a sender to reclaim or delay a payment, or for an owner to regain control through a recovery path set up in advance, was found. HIP-30 sent a quarter of new ONE issuance to a recovery multisig to fund repayment of bridge-hack losses; that was a governance fund, not a feature users could set on their own accounts. Nothing can execute since the halt. 1623 |
| Rollups | None found Earlier definition | No rollup settling to Harmony was found. The planned replacement ONE token is an ordinary token on Ethereum itself, not a Harmony layer 2. 22 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | None foundCurve (no value on Harmony), ViperSwap (inactive) | No exchange can operate on the halted chain. DefiLlama still lists former Harmony exchanges: on 27 September 2026 it showed Curve with no value locked on Harmony and ViperSwap with none at all, and put Harmony's whole total under $10,000. The full list of former exchanges was not reviewed. The migration does not recreate liquidity-pool positions. 20282930 |
| Issuer-native stablecoins | None found | Neither Circle's USDC list nor Tether's list of supported blockchains includes Harmony. Stablecoins on Harmony were bridged representations, such as 1USDC from Ethereum, and nothing can move on the halted chain. The migration FAQ says bridged assets will be claimable on their origin chains. 5203132 |
| Algorithmic stablecoins | None found | No stablecoin of any design can operate on the halted chain. Algorithmic stablecoin projects that may once have run on Harmony were not reviewed. 16 |
| Bridges | None foundLayerZero bridge (stopped with the chain), Horizon bridge (drained in 2022) | No bridge transfer to or from Harmony can complete after the halt. While it ran, Harmony's docs pointed users to a LayerZero-based bridge to Ethereum and BNB Chain; the earlier Horizon bridge lost about $100 million in June 2022, a theft the FBI attributed in January 2023 to North Korea's Lazarus Group. The migration FAQ plans claim contracts on origin chains for bridged assets and on Ethereum for ONE held on other chains. Risk: Horizon was reported to be guarded by a 2-of-5 multisig, so two stolen keys were enough to drain it, and tokens it had issued on Harmony lost their backing. Assets bridged to Harmony, and ONE-based tokens on other chains, now depend on claim contracts not verified as deployed. After the 11 August 2026 exploit the FAQ reports about 2.412 billion forged wrapped ONE still on BNB Smart Chain and 12.9 million on Ethereum, and says it will most likely use a pre-hack snapshot for those claims. 56720232425 |
| Block explorers | First-partyHarmony Explorer (Blockscout) | The explorer at explorer.harmony.one, now built on Blockscout and listed in the Ethereum chain registry, still serves history up to the final block of 10 September 2026 and reported no transactions on 27 September 2026. No second explorer was verified. Explorer data is provider-indexed, not consensus. 171819 |
| Hardware wallets | ThinLedger (through Harmony's tools or MetaMask), Trezor (through MetaMask or Rabby) | See the custody section: both vendors list Harmony, but the documented signing paths run through third-party software, and the chain no longer processes transactions. 93337 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Through an intermediaryHarmony's staking dashboard with the Harmony device app, or MetaMask with Ledger's Ethereum appSame as native: Unknown | Can: Hold the key for a Harmony address using the Harmony device app, which Harmony's docs say was for the Nano S only and installed through Ledger Live's developer mode Can: Sign Harmony transfers through MetaMask with Ledger's Ethereum app, as Harmony's docs describe, while the chain was running Cannot: Send, receive or stake ONE on Harmony: the chain has produced no blocks since 10 September 2026 Cannot: Count on Ledger Wallet itself: Ledger's Harmony page describes managing ONE there, but Ledger's currency definitions have no Harmony entry and Ledger archived its Harmony app repository in January 2025The Ethereum chain registry gives Harmony its own key-path coin type (1023). Whether accounts made with the Harmony device app appear under Ledger's default Ethereum path, where the migrated token would be held, was not tested. 89161933343536 |
| Trezor | Through an intermediaryMetaMask or Rabby, listed on Trezor's Harmony pageSame as native: No | Can: Keep the key for a Harmony Shard 0 address on a Trezor Safe 3, 5 or 7 and connect it to MetaMask or Rabby, as Trezor's Harmony page lists Cannot: Manage Harmony in Trezor Suite; Trezor's page says it is not supported there Cannot: Stake with a Trezor: Harmony's docs say Trezor signs through its Ethereum firmware and that staking would need Harmony-specific firmware that did not exist Cannot: Send or receive on Harmony: no blocks since 10 September 2026 101637 |
Public data
iKnow Blockchain has no public-data lookups for Harmony yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Migration snapshot taken and Harmony stops producing blocks
Four days after Harmony announced on X that it would retire its chain, the migration cutoff fell at 14:00 UTC on 10 September 2026 (shard 0 block 93,623,067, shard 1 block 95,882,100). Shard 0 produced its last block 41 minutes later and shard 1 stopped soon after; no blocks have followed. Balances are to be reissued as a new fixed-supply ONE token on Ethereum, with staked ONE moved to validator vaults, subject to thresholds and exclusions.
- Proposal:announced by Harmony on X on 2026-09-06, per press reports; no on-chain governance record found
- Implementation:snapshot taken; accounting toolkit published
- Release:replacement token source published; deployment not verified
- Activation:chain halted since 2026-09-10; distribution not verified
Sources: harmony-migration repository (polymorpher) — Harmony migration accounting (external site) · harmony-migration repository (polymorpher) — Harmony migration user FAQ (external site) · Harmony — Harmony shard 0 public RPC (external site) · Harmony — Harmony shard 1 public RPC (external site) · The Block — Harmony to fully sunset Layer 1, proposes token migration to Ethereum for AI video initiative (external site) · Harmony Community Forum — Voluntary winding down (external site)
-
Harmony rolls back to 11 August after an exploit and restarts on 20 August
After an exploit that the migration FAQ later called a forge-mint incident, Harmony released v2026.1.2, which rejects the abandoned blocks and known malicious blocks by hash and adds safeguards for an emergency restart. Validators replaced their databases with a clean copy ending at shard 0 block 92,730,034 and shard 1 block 94,978,278 and restarted on a coordinated signal, running v2026.1.3. On-chain timestamps show the next canonical shard-0 block at 13:51:41 UTC on 20 August 2026.
- Implementation:rollback executed
- Release:v2026.1.2 on 2026-08-15, v2026.1.3 on 2026-08-19
- Activation:chain restarted 2026-08-20
Sources: Harmony (GitHub) — Mainnet Release 2026.1.2 (external site) · Harmony (GitHub) — Reject abandoned branch hashes (#5106) (external site) · Harmony (GitHub, rollback-92730034 branch) — Node operator rollback guide (external site) · Harmony (GitHub, rollback-92730034 branch) — Validator rollout notes: shard-0 clean-database recovery (external site) · Harmony — Harmony shard 0 public RPC (external site) · harmony-migration repository (polymorpher) — Harmony migration user FAQ (external site)
-
Harmony v2026.1.1 fixes cross-shard receipt replay and a quorum-counting flaw
Harmony published node release v2026.1.1, whose only listed change is pull request 5101. Its commits fix two flaws. The signature check used for committees from before staking began counted every committee member instead of the members who actually signed, so a block with no signers and an empty signature could pass as having a quorum. And for receipts from blocks older than an earlier replay fix, the marker that records a cross-shard receipt as already used was built from unsigned fields, so a genuine receipt could be resubmitted with altered details and credited again on the receiving shard with no matching debit on the sending shard. The release notes do not call the upgrade mandatory and set no activation epoch.
- Implementation:fixes merged 2026-08-12 in pull request 5101
- Release:v2026.1.1 published 2026-08-12
- Activation:no hard fork or activation epoch stated; applied on nodes that installed it; uptake not verified
Sources: Harmony (GitHub) — Mainnet Release 2026.1.1 (external site) · Harmony (GitHub) — Cx receipt fixes main (#5101) (external site) · Harmony — Harmony shard 0 public RPC (external site) · Harmony (GitHub, rollback-92730034 branch) — Validator rollout notes: shard-0 clean-database recovery (external site) · The Block — Harmony to fully sunset Layer 1, proposes token migration to Ethereum for AI video initiative (external site)
-
Bloom hard fork brings newer Ethereum features to Harmony
Release v2026.1.0 scheduled the Bloom hard fork for epoch 2964 (shard 0 block 91,488,255). It enabled several Ethereum improvements, including transient storage (EIP-1153), BLS12-381 precompiles (EIP-2537), PUSH0 (EIP-3855), MCOPY (EIP-5656), limits on SELFDESTRUCT (EIP-6780) and block-hash history (EIP-2935), together with a second version of leader rotation, block timestamp checks and tighter cross-shard proof handling. Validators had to run accurate time synchronization.
- Implementation:Released
- Release:v2026.1.0 published 2026-07-08
- Activation:activated at epoch 2964 in mid-July 2026
Sources: Harmony (GitHub) — Mainnet Release 2026.1.0 (Bloom hard fork) (external site) · Harmony — Harmony shard 0 public RPC (external site) · Harmony — Q3 2025: London & Berlin Forks, Stream Sync Dashboards, LP Bots, Beta Governance (external site)
-
Harmony v2026.0.0 adds Stream Sync and sets shard constants to two
Harmony published node release v2026.0.0, a mandatory upgrade without a hard fork. It added Stream Sync, a peer-to-peer way to sync that removes reliance on DNS-based syncing but stayed optional, and changed configuration and consensus constants from four shards to two to match the network running since November 2023.
- Implementation:Released
- Release:v2026.0.0 published 2026-03-04
- Activation:no hard fork; took effect as nodes upgraded
Sources: Harmony (GitHub) — Mainnet Release 2026.0.0 (external site) · Harmony (GitHub) — Harmony releases (external site)
Topics your AI can explain
Your AI can explain these topics for Harmony through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Harmony's shutdown announcement of 6 September 2026 is known only from press reports (The Block, crypto.news) that link Harmony's X posts; X could not be read, and nothing appears on harmony.one, the docs or the blog. The halt comes from block data and community reports; the migration terms come from a repository kept by a Harmony core developer and from Harmony's own token-contract repository.
- Exact final-block heights, times, committee figures and the gas price come from the original author's reads of Harmony's public RPC and explorer on 27 September 2026; the verifier did not repeat those chain reads and checked them only against published sources.
- How the 11 August 2026 exploit worked is known only from press reports of Harmony's reconstruction (cross-shard receipts processed more than once, more than 3 trillion ONE minted in six transactions); no Harmony post-mortem document was read.
- The Ethereum address of the new ONE token, whether it has been deployed, and whether any distribution or vault has gone live were not verified.
- The size of the August 2026 rollback (141,628 shard-0 blocks, 109,126 ordinary and 315 staking transactions) comes from crypto.news citing Harmony's investigation, not from a primary Harmony document.
- Where the half of fees not sent to the community multisig under HIP-28 went (burned or otherwise) was not verified.
- Ledger's Harmony page describes managing ONE in Ledger Wallet, but Ledger's published currency definitions have no Harmony entry and Ledger's Harmony app repository is archived; direct support in Ledger Wallet is unconfirmed.
- The Horizon bridge's 2-of-5 multisig design comes from Elliptic's reporting, and the FBI attribution from CryptoSlate's report of the FBI statement; the FBI page and Harmony's own Horizon post-mortem blocked automated reading.
- DefiLlama's full list of former Harmony exchanges and algorithmic stablecoins was not reviewed; its protocol index is too large to read in one fetch.
- Validator operators were not identified. Committee and stake figures come from one public RPC read of the final epoch.
- The migration documents mention earlier incident contracts from May 2025 and April 2026; those incidents were not reviewed.
- The relationship between the AI video product now shown on harmony.one and the Harmony chain team was not verified.
- Absence of a light client, atomic-swap tool or channel layer before the halt was not exhaustively verified.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Consensus (external site)
- Effective Proof-of-Stake (external site)
- Sharding (external site)
- Requirements (external site)
- What token will I get after the bridge (external site)
- LayerZero Bridge (external site)
- LayerZero Bridge: Important Notice (external site)
- Ledger Nano: Download & Setup (external site)
- Ledger with Metamask (external site)
- Trezor (external site)
- harmony-one/harmony: the core protocol of Harmony (external site)
- Mainnet Release 2023.3.0 (HIP-30 hard fork) (external site)
- Mainnet Release 2024.3.1 (HIP-32 phase 1) (external site)
- Node operator rollback guide (rollback-92730034 branch) (external site)
- Reject abandoned branch hashes (#5106) (external site)
- Harmony shard 0 public RPC (block, epoch, committee and node metadata reads) (external site)
- Harmony Mainnet blockchain explorer (external site)
- Harmony explorer statistics API (external site)
- Harmony Mainnet Shard 0 chain record (eip155-1666600000) (external site)
- Harmony migration user FAQ (external site)
- Harmony migration accounting (external site)
- HarmonyONEToken.sol (external site)
- HIP30v2: Harmony's Network Evolution and Token Redistribution (external site)
- FBI: Lazarus Group carried out Harmony's Horizon Protocol attack (reports the FBI statement of 23 January 2023) (external site)
- Over $1 billion stolen from bridges so far in 2022 as Harmony's Horizon Bridge becomes latest victim in $100 million hack (external site)
- Harmony to fully sunset Layer 1, proposes token migration to Ethereum for AI video initiative (external site)
- Harmony plans to sunset layer 1 and migrate ONE token to Ethereum (external site)
- DefiLlama protocols API (external site)
- DefiLlama chains API (value locked per chain) (external site)
- DefiLlama value locked: ViperSwap (external site)
- USDC contract addresses (external site)
- Supported protocols (external site)
- Harmony Wallet (external site)
- @ledgerhq/cryptoassets currency definitions (v13.56.0) (external site)
- LedgerHQ/app-harmony-one (archived 2 January 2025) (external site)
- Ledger with Staking Dashboard (external site)
- Harmony wallet (external site)
- Harmony: The Remix Economy for AI Video (external site)
- Harmony's Newsletter archive (external site)
- Slashing and Uptime (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding