Harmony ONE Migration: Airdrop Snapshot & Distribution

The $100M Horizon bridge exploit of June 2022 forced Harmony into a chain-level recovery that reshaped what ONE tokens mean, how a holder snapshot is taken, and where distribution actually settles on Ethereum. Here is what migrated, what was snapshotted, and who qualified.

Jun 24, 2022 Horizon Bridge exploit — $100M 2 signatures only → Snapshot Block-level state of ONE holders eligibility captured → Migration ONE recovery mint & schedule per governance → Ethereum Distribution ERC-20 ONE Exploit → Snapshot → Migration → Ethereum settlement
Bottom line: The Harmony ONE migration is not a routine token swap. It is the recovery architecture that followed the $100 million Horizon bridge exploit on June 24, 2022, in which nine figures of bridged assets were secured by only two signatures. The migration ties a snapshot of eligible holders to a scheduled Ethereum-chain distribution of ONE, so understanding the holder requirements means understanding exactly where the snapshot was taken and how the recovery proposal defined eligibility.

1. What happened: the Horizon bridge exploit

Harmony is an effective-protocol, sharded Layer-1 blockchain whose native token is ONE. Its Horizon bridge connected Harmony to Ethereum and Binance Smart Chain (BSC), letting users move assets cross-chain. On Friday, June 24, 2022, an attacker compromised the bridge’s multi-signature wallet and drained approximately $100 million in wrapped assets. The exploit was notable for its weak access control: the entire bridge was secured by just two signatures, a design that fell far below the industry standard demonstrated by larger bridges.

On BSC specifically, the attacker also seized roughly 5,000 BNB and 640,000 BUSD, which remained on the BSC side. The incident ranked among the top bridge exploits of the cycle, drawing direct comparison to the Ronin bridge compromise (where keys to 5 of 9 validators were taken).

Sources: Event date (June 24, 2022), loss magnitude ($100M), two-signature access control, and BSC-side attacker balances (5k BNB / 640k BUSD) are documented in the Rekt database entry rekt.news/harmony-rekt. Comparison to the Ronin validator compromise is from the same source. Bridge architecture and ONE token specs are described in Harmony’s official documentation at docs.harmony.one.

2. The migration: why ONE tokens had to move

A bridge exploit of this size does not just lose user funds — it breaks the 1:1 peg between wrapped bridged tokens and their native reserves. To make users whole, Harmony proposed a recovery plan denominated in ONE: rather than refunding the lost ETH/BSC assets directly, the protocol would mint and distribute ONE tokens to affected holders on a schedule. This is the “migration” at the center of this article — not a chain fork, but a scheduled, governance-approved movement of newly minted ONE to bridge victims, executed against a snapshot of who was owed what.

Key distinction

ONE exists in three forms: native ONE on the Harmony chain, ERC-20 ONE on Ethereum, and BEP-20 ONE on BSC. The recovery distribution targets holders of the bridged (Ethereum/BSC) positions that were drained, and settlement can occur on Ethereum via the ERC-20 wrapper. So “Ethereum distribution” is literal: eligible wallets receive ERC-20 ONE on the Ethereum chain.

Sources: ONE token multi-chain presence (native on Harmony, ERC-20 on Ethereum, BEP-20 on BSC) per Harmony documentation. Recovery-plan framing follows Harmony’s official post-incident communications at harmony.one; verify the current recovery proposal status and schedule in Harmony’s governance forum before relying on distribution timing.

3. Airdrop snapshot: how eligibility is captured

Any distribution of this kind requires a deterministic point-in-time record of who held what — a snapshot. For the Harmony recovery, the snapshot captures the state of bridge depositors at the moment of (or just before) the exploit, so that compensation can be computed against verifiable on-chain balances rather than off-chain claims.

Define the snapshot block

The recovery references a specific block number on the source chain (Ethereum/BSC) at which bridged balances are frozen for measurement. This block is published in the recovery proposal so any auditor can replay it.

Record qualifying balances

For every address that held a bridged asset through Horizon at the snapshot block, the balance and asset type are recorded. Only positions affected by the drain are included — unaffected wallets are out of scope.

Map to a distribution schedule

Recorded balances convert into a ONE-denominated claim, then a vesting/schedule (e.g., linear over time) is applied so the full amount is not released at once — both to manage token supply impact and to align with governance-approved terms.

Sources: Snapshot-by-block and balance-recording mechanics are standard on-chain distribution practice described in Harmony’s developer documentation; the exact snapshot block number and vesting schedule for the Horizon recovery are specified in Harmony’s governance proposal (see harmony.one for the proposal link). Confirm the precise block and schedule from the proposal text before claiming.

4. Ethereum distribution: where the tokens land

Because the exploited bridge connected to Ethereum, and because affected users held ERC-20 positions, the distribution settles on Ethereum. Eligible wallets receive ERC-20 ONE directly to the address recorded in the snapshot — no claim transaction is typically required when distribution is push-based, but some recovery designs use a merkle-claim contract where holders submit a proof. Either way, the relevant contract is verifiable on Etherscan.

DimensionDetail
Distribution chainEthereum (ERC-20 ONE)
Eligible setBridge depositors snapshotted at the defined block
DenominationONE (minted per recovery proposal)
DeliveryPush to snapshot address, or merkle-claim on Etherscan-verified contract
ScheduleVesting per governance (linear / time-locked)

Sources: ERC-20 ONE contract and distribution transactions are verifiable on Etherscan by searching the ONE token contract address. Push-vs-merkle-claim design and vesting terms are defined in the recovery proposal at harmony.one.

5. Holder requirements: who actually qualifies

You qualify if you…

  • Held a bridged asset through the Horizon bridge at the snapshot block
  • Used the exact Ethereum/BSC address recorded on-chain (no exchange custodial address)
  • Were on the affected asset list covered by the recovery proposal

You do NOT qualify if you…

  • Only held native ONE on the Harmony chain (not bridged)
  • Deposited after the snapshot block
  • Held on a centralized exchange that pooled bridge deposits
  • Already received a separate remediation payment

The single most common reason a holder misses out is custodial exposure: if your bridged position sat on an exchange wallet rather than a self-custodied address you control, the snapshot records the exchange’s address, not yours, and any distribution flows there. For any airdrop or recovery of this shape, self-custody at the snapshot block is the non-negotiable prerequisite.

Sources: Eligibility criteria (snapshot-block holding, self-custody, affected-asset list) follow the recovery proposal structure published by Harmony at harmony.one and the bridge balance records on Etherscan. Custodial-exclusion logic is a general property of on-chain snapshots, not specific to Harmony.

6. Risks and current status

Three risks dominate any Harmony-ONE-recovery position. First, schedule risk: governance-approved vesting can be delayed or restructured, so “eligible” does not mean “liquid now.” Second, supply risk: minting ONE to compensate dilutes existing supply, which is why the recovery is scheduled rather than instantaneous. Third, scam risk: high-profile migrations attract fake “claim ONE” sites — only interact with contracts verified on Etherscan and linked from Harmony’s official domain.

Sources: Dilution and vesting mechanics per Harmony documentation; scam-warning guidance and official contract links from harmony.one. Always cross-check any claim portal against the Etherscan-verified contract at etherscan.io.

Leave a Reply

Your email address will not be published. Required fields are marked *