Harmony (ONE)
Harmony is an EVM-compatible, sharded Layer 1 blockchain, and ONE is its protocol-native asset used for transaction fees, staking and value transfer.
BitcoinToolkit separates CoinGecko aggregated ONE/USD data from the Binance Spot ONE/USDT market and explains ONE units, gas, account-based execution, sharding, EPoS and FBFT finality.
- Snapshot:
- CoinGecko - USD
- Chart:
- Binance Spot - ONE/USDT
- Timezone:
- UTC
Use this page as an educational network and market reference. It is not an executable exchange quote, validator instruction, price forecast or trading recommendation.
Harmony Candlestick Chart
ONE/USDT · Binance Spot · UTC
Long ranges automatically use a compatible candle interval.
Historical Binance Spot candles are available. JavaScript is required for current-candle updates.
Recent OHLC and volume data
| Time (UTC) | Open (USDT) | High (USDT) | Low (USDT) | Close (USDT) | Volume (ONE) |
|---|---|---|---|---|---|
| Aug 25, 2026 17:00:00 UTC | 0.00 USDT | 0.00 USDT | 0.00 USDT | 0.00 USDT | 34,805,122.40 ONE |
| Aug 25, 2026 16:00:00 UTC | 0.00 USDT | 0.00 USDT | 0.00 USDT | 0.00 USDT | 27,106,537.50 ONE |
| Aug 25, 2026 15:00:00 UTC | 0.00 USDT | 0.00 USDT | 0.00 USDT | 0.00 USDT | 18,521,642.70 ONE |
| Aug 25, 2026 14:00:00 UTC | 0.00 USDT | 0.00 USDT | 0.00 USDT | 0.00 USDT | 35,300,224.30 ONE |
| Aug 25, 2026 13:00:00 UTC | 0.00 USDT | 0.00 USDT | 0.00 USDT | 0.00 USDT | 63,839,795.80 ONE |
Market data: Binance Spot ONE/USDT
Charting library: TradingView Lightweight Charts
Harmony Network and ONE
Harmony is the sharded network, ONE is its protocol-native asset, and contract-token balances are maintained in smart-contract state.
Harmony
Harmony (ONE): ONE pays transaction execution fees on Harmony.
Harmony (ONE): Validators and delegators use ONE in Harmony Effective Proof of Stake.
ONE/USDT
EVM Layer 1
Harmony is an EVM-compatible Layer 1 network that divides network, transaction and state processing across shards.
Native ONE belongs to protocol account state and pays network fees; contract-token balances belong to token-contract storage.
Harmony Accounts
Harmony uses account-based EVM state with balances, nonces, contract code and persistent contract storage.
Each shard maintains account state that changes when valid transactions execute.
A private key controls an externally owned account and signs transactions.
Contract accounts contain deployed EVM bytecode and execute when called.
A sender nonce orders transactions and prevents replay on the applicable shard.
An account balance records native ONE available for transfers and gas fees.
Harmony executes EVM-compatible bytecode against the state of the target shard.
Contracts maintain persistent storage after successful execution and block commitment.
ONE Units
One ONE equals 1,000,000,000 nano or 1,000,000,000,000,000,000 atto.
Wallets display ONE, fee interfaces may use nano, and raw Harmony values are represented in integer atto.
Harmony Gas and Fees
Harmony meters EVM-compatible computation in gas and charges the execution fee in native ONE.
ONE
Gas measures computation and storage work requested by a transaction.
The gas limit caps the work a transaction may consume.
Gas used records the work consumed by execution.
The gas price states the amount of ONE-denominated atto offered per gas unit.
Execution cost equals gas used multiplied by gas price and is paid in ONE.
Harmony Transactions
A Harmony transaction is created for a shard, signed, validated, propagated, executed, included in a block and finalized through FBFT.
- Transaction creationThe sender sets the shard, recipient, value, data, nonce and gas parameters.
- SigningThe sender signs the transaction with the account private key.
- Nonce validationNodes validate the signature, nonce, balance, shard fields and transaction rules.
- BroadcastThe signed transaction is submitted to a Harmony RPC endpoint for the selected shard.
- Node propagationValid transactions propagate among nodes serving the shard.
- ExecutionThe EVM applies the transaction against shard state and meters gas.
- Receipt generationExecution produces a receipt containing status, gas usage and logs.
- Block inclusionA shard committee leader proposes a block containing accepted transactions.
- Finality stateMore than two-thirds of committee voting power signs the block through FBFT before it is committed.
Harmony Smart Contracts
Harmony supports EVM-compatible contracts while adding shard-aware transaction behavior.
Contract accounts contain deployed bytecode and have no private signing key.
Compiled EVM bytecode executes under Harmony shard and gas rules.
Contracts read and update persistent state in the shard where they execute.
Calls can transfer native ONE and pass encoded input to contract functions.
Token contracts maintain balances and allowances independently from native ONE.
Native ONE pays protocol gas; contract tokens cannot automatically replace ONE as the fee asset.
Harmony EPoS, FBFT and Finality
Harmony uses Effective Proof of Stake to elect shard committees and Fast Byzantine Fault Tolerance to commit blocks after a supermajority vote.
Harmony combines Effective Proof of Stake validator election with shard-level Fast Byzantine Fault Tolerance consensus.
Elected validator BLS keys are assigned to shard committees with voting power derived from effective stake.
A committee leader proposes a block and coordinates announce, prepare and commit phases.
Committee validators verify and sign the block hash using BLS signatures during prepare and commit phases.
A block is committed after signatures representing more than two-thirds of committee voting power are collected in the FBFT commit process.
Applications should use the current shard RPC result and cross-shard receipt status rather than assuming every cross-shard action completes in one local block.
How This Page Was Checked
Technical terminology and market-source labels are checked against primary documentation.
- Harmony EPoS, sharding and FBFT terminology is checked against official documentation.
- Protocol and market-data sources are reviewed separately.
- ONE units and gas roles are checked against Harmony technical documentation.
Market Data Methodology
The snapshot is CoinGecko aggregated USD data. The chart is Binance Spot ONE/USDT data. Provider coverage and quote currencies differ, so displayed values can differ.
- Market Snapshot Source
- CoinGecko aggregated market data (USD)
- Candlestick Source
- Binance Spot market data
- Pair
- ONE/USDT
- Venue
- Binance Spot
- Market Type
- Spot
- Timezone
- UTC
- Cache
- Snapshot cache is approximately 60 seconds; historical candle cache varies by interval.
- Failure Handling
- Verified cache is labeled Cached or Delayed. Missing values remain unavailable.
- Snapshot Status
- Delayed
- Chart Status
- Historical Only
- Report Issue
- Report a market-data problem →
Known Limitations
- CoinGecko USD and Binance Spot ONE/USDT are separate datasets.
- Cross-shard behavior and application support can differ from same-shard EVM transactions.
- Applications should use current Harmony documentation and RPC responses for shard and confirmation policies.
Technical Sources
Protocol claims use official Harmony documentation. Market data retains separate provider attribution.
Harmony protocol and developer references
Market data references
Harmony FAQ
Answers to common questions about Harmony, ONE, gas, sharding, EPoS and FBFT finality.
What is Harmony?
Harmony is an EVM-compatible Layer 1 network that shards network, transaction and state processing.
What is ONE used for?
ONE is Harmony's native asset for transaction fees, staking, delegation and value transfer.
How are Harmony gas fees paid?
Harmony meters EVM execution in gas and charges the resulting fee in native ONE.
What are atto and nano?
Atto is the smallest ONE unit and nano equals one billion atto.
How does Harmony finality work?
Harmony shard committees use FBFT and commit a block after more than two-thirds of voting power signs it.
Editorial Information
Verified technical content, reviewed sources and update history.
- Published
- Last Review
- Data Verification
- Sources
- Official documentation