On this page
Harmony is a smart-contract blockchain whose native asset, ONE, pays network fees and participates in proof-of-stake security. Its technical documentation and ecosystem tools remain available as of October 8, 2026. The important change from early descriptions is that a review must account for bridge history and distinguish native ONE from assets represented on Harmony through a separate bridge.
What Harmony was built to do
The project pursued low-cost application execution using sharding, a design that divides work across parts of a network, and a consensus system called Effective Proof of Stake. Its documentation describes a method intended to reduce the advantage of very large stakes when allocating validator participation. That is a design objective, not proof that concentration can never develop.
For an application developer, compatibility with the Ethereum Virtual Machine can make familiar contract tools usable. Compatibility does not make an application run on Ethereum itself. Transactions still depend on Harmony's validators, network configuration and available infrastructure.
Early throughput claims often assume a particular configuration or test. They should not be read as a promise of what any application will achieve. User-facing performance also depends on wallet access, remote procedure call services, the complexity of the contract and the reliability of the application's own interface.
ONE and staking
ONE is the network asset, rather than a stablecoin or a claim on a company's profits. Staking connects the asset to consensus: validators operate the infrastructure that proposes and checks blocks, while delegators can assign stake to validators. Rewards and penalties depend on protocol rules and validator behavior.
Harmony's staking documentation explains that returns are not fixed and vary with validator performance and network participation. A headline staking rate is therefore incomplete without commissions, lockup or unbonding conditions, and the possibility of penalties. Receiving more ONE also does not establish a gain in purchasing power.
Native issuance and transaction fees support network economics. An old maximum-supply assumption or a supply number copied from a 2019 profile is not an adequate description of today's circulating balance. This page avoids a live supply figure and directs attention to the distinction between issuance rules and the amount actually circulating.
The Horizon incident changed the context
The Horizon bridge suffered a major incident in June 2022. Elliptic's analysis describes compromised private-key security and a phishing attack that gave attackers access to infrastructure. This was a bridge security failure, which is analytically distinct from an attacker taking over Harmony's base-layer consensus.
That distinction does not make the consequences less important. A bridged asset can represent collateral held elsewhere. If the collateral is missing or inaccessible, the token on the destination chain can continue to exist without retaining the expected redemption value. A familiar dollar-denominated name or ticker is not proof of full backing.
New bridges do not erase old asset histories
Harmony now publishes LayerZero bridge documentation explaining lock-and-mint or burn-and-release flows and the identification of destination token contracts. These instructions should not be confused with the old Horizon interface or with a promise that every legacy bridged asset is recoverable at its original value.
The receiving contract matters. A native asset, a wrapped version issued by one bridge and an older representation issued by another bridge can be economically different even when their labels look similar. Wallet software may display all three without explaining the custody or redemption assumptions behind them.
What to examine before using the network
A practical review starts with the actual asset: native ONE, an application token or a bridged claim. It then considers the validator or application being used, wallet support and the route needed to exit. Bridging introduces another system whose security needs assessment; it should not be treated as a routine change of address format.
Harmony remains useful to study as a network combining Ethereum-style applications with its own consensus design. Its history also offers a concrete lesson: a blockchain can continue processing transactions while a connected financial product fails. The Kava profile examines another approach to connecting application environments, with different architecture and risks.