← Harmony ONE (Protocol Entity)reviewed 2026-09-07 · 41 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Harmony ONE (Protocol Entity) against the sources the page cites. Only the most recent review is shown.
Read this first
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
2 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #33[disputed][awaiting moderator]in section: Chain Rollback — Centralisation and Immutability Concerns
“As of August 21, 2026, both shards were reported stable and advancing through normal epoch progression.”
reviewerAs of August 21, 2026, both shards were reported stable and advancing through normal epoch progression.Multiple independent outlets, including the page's own cited source (CoinMarketCap), date the rollback-complete/stable announcement to August 22, 2026, one day after what the page states.Proposed correction (not yet applied)As of August 22, 2026, both shards were reported stable and advancing through normal epoch progression. - #41[disputed][awaiting moderator]in the timeline
“2026-08-21”
reviewerThe rollback was reported complete on 2026-08-21, with both shards stable for 24+ hours and advancing from epoch 3002 to 3004.The event content (epoch progression, 24+ hour stability, near-full signing participation) is accurate, but it occurred and was reported on August 22, 2026, not August 21 as stored — including by the entry's own cited source.Proposed correction (not yet applied)2026-08-22
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #29[unverifiable][awaiting moderator]in section: August 2026 Price Impact and Token Dilution
“By the morning of August 13 in European trading hours the token had partially recovered to approximately $0.0007681, reflecting a rebound of approximately 34% from the low.”
reviewerBy the morning of August 13 European hours, ONE had recovered to approximately $0.0007681, a ~34% rebound from the low.The overall recovery trend is corroborated, but the specific $0.0007681 figure and precise 34% rebound could not be independently verified in any source consulted.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Protocol Overview
“Tse holds a PhD in cryptographic protocols from the University of Pennsylvania and previously held engineering roles at Google and Apple.”
reviewerTse holds a PhD in cryptographic protocols from the University of Pennsylvania and previously held engineering roles at Google and Apple.The Google/Apple career claim is confirmed, but multiple bios describe Tse's UPenn doctorate as being in security protocols and compiler verification, a narrower and different framing than 'cryptographic protocols.' - #35[partially supported][awaiting moderator]in section: Chain Rollback — Centralisation and Immutability Concerns
“The team deployed replacement databases for affected shards rather than using the standard revert function, which Harmony stated 'mainly moves chain heads and does not fully clear later receipts, indexes, snapshots and cross-shard information.'”
reviewerHarmony deployed replacement databases rather than the standard revert function, stating the revert function 'mainly moves chain heads and does not fully clear later receipts, indexes, snapshots and cross-shard information.'The substance and rationale are corroborated, but the wording found in secondary reporting ('does not fully remove... snapshots, or cross-shard data') differs slightly from the page's quoted phrasing ('does not fully clear... snapshots and cross-shard information'); the exact original wording of Harmony's statement could not be independently confirmed since it could not be verified against a primary Harmony source. - #40[partially supported][awaiting moderator]in the timeline
“Validators activate second stage of the rollback procedure.”
reviewerValidators activated the second stage of the rollback procedure on August 20, 2026.The underlying fact (second-stage activation on August 20) is independently confirmed by KuCoin Flash reporting, but the timeline entry's cited source (CryptoRank) does not itself contain this detail, so the citation is mismatched to the claim.
confirmed
35 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“Harmony (ONE) is a layer-1 sharded proof-of-stake blockchain founded in 2017 and launched on mainnet in June 2019.”
reviewerHarmony is a layer-1 sharded proof-of-stake blockchain founded in 2017 and launched on mainnet in June 2019.Founding year and mainnet launch month are consistently reported across independent sources. - #2[confirmed][no action needed]in the summary
“The 2026 incident drove the ONE token to an all-time low of $0.0005735 and prompted an unilateral chain rollback erasing over 109,000 confirmed transactions, raising systemic concerns about the network's security architecture and degree of decentralisation.”
reviewerThe 2026 exploit drove ONE to an all-time low of $0.0005735 and prompted a unilateral chain rollback erasing over 109,000 confirmed transactions.ATL price and transaction-erasure figure are corroborated by multiple independent outlets (DailyCoin, Crowdfund Insider, IDOSLaunchpad). - #3[confirmed][no action needed]in section: Protocol Overview
“The protocol was founded by Stephen Tse in 2017.”
reviewerHarmony was founded by Stephen Tse in 2017.Confirmed by founder interview and multiple secondary bios. - #5[confirmed][no action needed]in section: Protocol Overview
“Harmony raised approximately $18 million in a seed round and an additional $5 million via a Binance Launchpad IEO in May 2019, which was priced at $0.00318 per ONE token.”
reviewerHarmony raised approximately $18 million in a seed round and $5 million via a May 2019 Binance Launchpad IEO priced at $0.00318 per ONE.Figures match independent reporting closely; IEO price rounds correctly from $0.003175. - #6[confirmed][no action needed]in section: Protocol Overview
“The mainnet launched in June 2019, with staking enabled in May 2020.”
reviewerMainnet launched June 2019, with staking enabled in May 2020.Both dates corroborated by press coverage. - #7[confirmed][no action needed]in section: Protocol Overview
“The ONE token reached an all-time high of approximately $0.379 in October 2021.”
reviewerONE reached an all-time high of approximately $0.379 in October 2021.Confirmed by multiple price-tracking sources. - #8[confirmed][no action needed]in section: 2022 Horizon Bridge Hack — FBI-Attributed to Lazarus Group
“On June 24, 2022, Harmony's cross-chain Horizon Bridge was exploited and approximately $99.6 million in cryptoassets was stolen, including WETH, USDC, USDT, DAI, SUSHI, and AAVE.”
reviewerThe Horizon Bridge was exploited June 24, 2022 for approximately $99.6 million including WETH, USDC, USDT, DAI, SUSHI, and AAVE.Directly corroborated by Elliptic's own hack summary. - #9[confirmed][no action needed]in section: 2022 Horizon Bridge Hack — FBI-Attributed to Lazarus Group
“The theft occurred across 14 transactions on Ethereum and Binance Smart Chain and was caused by the compromise of private keys used to control a multisig wallet securing the bridge.”
reviewerThe theft occurred across 14 transactions and was caused by compromised private keys controlling the bridge multisig.Consistent across Elliptic and CFR write-ups. - #10[confirmed][no action needed]in section: 2022 Horizon Bridge Hack — FBI-Attributed to Lazarus Group
“Blockchain analytics firm Elliptic attributed the attack to APT38, also known as the Lazarus Group, within days of the incident.”
reviewerElliptic attributed the attack to APT38/Lazarus Group within days of the incident.Directly stated by Elliptic. - #11[confirmed][no action needed]in section: 2022 Horizon Bridge Hack — FBI-Attributed to Lazarus Group
“In January 2023, the United States Federal Bureau of Investigation formally confirmed that Lazarus Group — a state-sponsored threat actor operating on behalf of the Democratic People's Republic of Korea (DPRK) — was responsible for the theft.”
reviewerIn January 2023 the FBI formally confirmed Lazarus Group (DPRK-linked) responsibility for the theft.FBI press release URL returned 403 to automated fetch but is corroborated by numerous secondary outlets quoting it directly (TheHackerNews, BleepingComputer, TechCrunch, Elliptic). - #12[confirmed][no action needed]in section: 2022 Horizon Bridge Hack — FBI-Attributed to Lazarus Group
“In January 2023, approximately $60 million was moved through the Ethereum privacy protocol Railgun.”
reviewerApproximately $60 million in stolen ETH was moved through Railgun in January 2023.Matches FBI's own dated account. - #13[confirmed][no action needed]in section: 2022 Horizon Bridge Hack — FBI-Attributed to Lazarus Group
“Harmony offered a $1 million bounty for the return of funds and stated it would advocate for no criminal charges if funds were returned.”
reviewerHarmony offered a $1 million bounty for return of funds and stated it would advocate for no criminal charges.Verified against Harmony's original announcement. - #14[confirmed][no action needed]in section: 2022 Horizon Bridge Hack — FBI-Attributed to Lazarus Group
“The U.S. Department of the Treasury's Office of Foreign Assets Control had previously sanctioned the Lazarus Group in 2019.”
reviewerOFAC previously sanctioned the Lazarus Group in 2019.Confirmed via Federal Register notice of OFAC sanctions action. - #15[confirmed][no action needed]in section: Post-2022 Recovery Efforts
“The programme involved using treasury funds to reimburse depegged assets over a four-year horizon through a token burn mechanism.”
reviewerThe recovery programme used treasury funds to reimburse depegged assets over a four-year horizon via a burn mechanism.Matches the forum's own description of the recovery mechanism. - #16[confirmed][no action needed]in section: Post-2022 Recovery Efforts
“The Recovery ONE Foundation entered a burn phase in 2023 in coordination with ecosystem partners including Modulo and Tranquil Finance.”
reviewerThe Recovery ONE Foundation entered a burn phase in 2023 with partners including Modulo and Tranquil Finance.The original burn-phase concept dates to October 2022, but the specific burn phase described (with Modulo/Tranquil Finance as partners) launched in 2023 as stated. - #17[confirmed][no action needed]in section: Post-2022 Recovery Efforts
“Multiple funding rounds were distributed through the Recovery ONE mechanism, with Round 10 in July 2023 allocating $100,000 among burn partners.”
reviewerRound 10 in July 2023 allocated $100,000 among burn partners.Exact figure and month match the source (accessed via search-cached summary; direct fetch returned 403). - #18[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“On August 12, 2026, an attacker exploited multiple compounding vulnerabilities in Harmony's consensus layer to fraudulently mint ONE tokens without corresponding debits.”
reviewerOn August 12, 2026, an attacker exploited compounding consensus-layer vulnerabilities to mint ONE without corresponding debits.Corroborated by independent technical analysis. - #19[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“Harmony's official incident update published on August 13, 2026 confirmed the attack began at approximately 23:25:40 UTC on August 11, with the first confirmed activity on Shard 0 at block 92,730,036.”
reviewerThe attack began at approximately 23:25:40 UTC on August 11, with first confirmed activity on Shard 0 at block 92,730,036.The primary X post could not be fetched directly (paywalled), but timing and block figures are corroborated by secondary reporting. - #20[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“Two waves of minting were identified: an initial wave of approximately 4 billion ONE across two empty-block transactions (1 billion ONE at block 92,731,152 and 3 billion ONE at block 92,732,898), and a fuller accounting of approximately 3.01 trillion ONE across six forged cross-shard transactions into four exploiter wallets.”
reviewerTwo minting waves occurred: ~4 billion ONE in an initial wave (1B + 3B at specific blocks), later revised to ~3.01 trillion ONE across six transactions into four wallets.Both the initial 4B figure and the later 3.01T revision are widely corroborated. - #21[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“First, a quorum verification bypass: the function IsQuorumAchievedByMask() compared the full committee's public key count against a threshold rather than counting actual signatures in the bitmap, meaning an all-zero bitmap with an identity aggregate BLS signature could satisfy quorum for pre-staking committees.”
reviewerVerichains identified a quorum verification bypass in IsQuorumAchievedByMask() allowing an all-zero bitmap with identity BLS signature to satisfy quorum.Near-verbatim match to the technical source. - #22[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“Second, unsigned Merkle proof identity fields: cross-shard receipt proofs contained ShardID and BlockNum as separate, unsigned copies of header fields, allowing attackers to mutate these values while keeping the BLS signature and header byte-identical, enabling the same receipt to be replayed with different identities.”
reviewerCross-shard receipt proofs contained unsigned ShardID and BlockNum fields, allowing receipt replay with mutated identity.Confirmed against the cited technical analysis. - #23[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“Third, weak replay protection logic: the Bloom hard fork's improved spent-marker system checked the epoch inside the proof's own header rather than the current chain epoch, leaving pre-fork receipts vulnerable to the legacy replay path keyed to mutable unsigned fields.”
reviewerThe Bloom hard fork's replay protection checked the epoch inside the proof's own header rather than the current chain epoch, leaving pre-fork receipts vulnerable.Confirmed against the cited technical analysis. - #24[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“Approximately 2.8 billion ONE tokens moved to intermediate attacker-controlled addresses within minutes of minting, and approximately 97% of minted tokens moved toward exchange deposit addresses according to reporting by TechTimes.”
reviewerApproximately 2.8 billion ONE moved to intermediate addresses within minutes, and ~97% of minted tokens moved toward exchange deposit addresses.TechTimes URL returned 403 to direct fetch (likely bot-blocking) but content is corroborated via search results and secondary citations. - #25[confirmed][no action needed]in section: August 2026 Cross-Shard Mint Exploit — Consensus-Layer Failure
“Harmony deployed emergency patch v2026.1.1 on August 12 at 06:30 UTC and halted Shard 0 at block 92,753,555 to prepare for rollback.”
reviewerHarmony deployed patch v2026.1.1 on August 12 at 06:30 UTC and halted Shard 0 at block 92,753,555.Patch version/timing independently confirmed; the specific halt block was not found in a secondary source but is not contradicted. - #26[confirmed][no action needed]in section: August 2026 Price Impact and Token Dilution
“The token reached an all-time low of $0.0005735 according to multiple sources, representing a decline of between 29% and 51% within hours of the incident.”
reviewerONE hit an all-time low of $0.0005735, a decline of between 29% and 51% within hours.Reported declines varied by outlet (29%-51%) depending on measurement window, matching the page's stated range. - #27[confirmed][no action needed]in section: August 2026 Price Impact and Token Dilution
“At the time of the crash the token was already approximately 99.8% below its all-time high of $0.379, set in October 2021.”
reviewerAt the crash, the token was approximately 99.8% below its all-time high of $0.379.Arithmetically consistent: (0.379 - 0.0005735) / 0.379 ≈ 99.85%, matching the stated 'approximately 99.8%'. - #28[confirmed][no action needed]in section: August 2026 Price Impact and Token Dilution
“The approximately 4 billion ONE minted in the initial wave represented roughly 26% of the circulating supply, constituting severe inflationary dilution.”
reviewerThe ~4 billion ONE minted in the initial wave represented roughly 26% of circulating supply.Consistent with independent secondary reporting. - #30[confirmed][no action needed]in section: Chain Rollback — Centralisation and Immutability Concerns
“Shard 0 was reverted to block 92,730,034 and Shard 1 to block 94,978,278, both timestamped at 23:25:37 UTC on August 11, 2026 — moments before the first confirmed forged mint.”
reviewerOn approximately August 17-18, 2026, Harmony announced and began executing a rollback to pre-attack checkpoints (Shard 0: block 92,730,034; Shard 1: block 94,978,278), both timestamped 23:25:37 UTC Aug 11.Checkpoint block numbers confirmed by multiple independent outlets. - #31[confirmed][no action needed]in section: Chain Rollback — Centralisation and Immutability Concerns
“The rollback eliminated more than 109,000 regular transactions and 315 staking transactions that had been confirmed after those checkpoints.”
reviewerThe rollback eliminated more than 109,000 regular transactions and 315 staking transactions.Matches independently sourced figures (109,126 regular, 315 staking). - #32[confirmed][no action needed]in section: Chain Rollback — Centralisation and Immutability Concerns
“Approximately 95.8% of discarded transactions were classified as automated, with DEX automation accounting for approximately 99,863 of the erased transactions.”
reviewerApproximately 95.8% of discarded transactions were automated, with DEX automation accounting for approximately 99,863 erased transactions.Precise figures match secondary reporting almost exactly. - #34[confirmed][no action needed]in section: Chain Rollback — Centralisation and Immutability Concerns
“Crowdfund Insider reported that the action raised direct concerns about blockchain immutability and decentralisation.”
reviewerCrowdfund Insider reported that the rollback action raised direct concerns about blockchain immutability and decentralisation.Directly confirmed by the cited article's own framing. - #36[confirmed][no action needed]in section: Tokenomics and Supply History
“The ONE token has a stated maximum supply of 12.6 billion tokens.”
reviewerThe ONE token has a stated maximum supply of 12.6 billion tokens, with annual issuance of 441 million ONE and fees burned.Tokenomics figures confirmed across multiple sources. - #37[confirmed][no action needed]in section: Tokenomics and Supply History
“A prior seed round raised approximately $18 million from investors including Lemniscap, Consensus Capital, UniValues Associates, and BCA Fund.”
reviewerThe seed round raised approximately $18 million from investors including Lemniscap, Consensus Capital, UniValues Associates, and BCA Fund.Investor list confirmed against independent reporting. - #38[confirmed][no action needed]in the timeline
“Harmony ONE IEO launched on Binance Launchpad at $0.00318 per token, raising $5 million.”
reviewerHarmony ONE IEO launched on Binance Launchpad on May 29, 2019.The Binance Launchpad session for Harmony ran across May 27-29, 2019; the stored date of May 29 is defensible as the sale-completion date but the cited Coinspeaker article specifically describes a May 27 launch, so the date is not unambiguous. - #39[confirmed][no action needed]in the timeline
“Harmony launches staking, becoming the first sharded blockchain to offer staking.”
reviewerHarmony launched staking on May 16, 2020, becoming the first sharded blockchain to offer staking.Directly confirmed by Harmony's own press release headline and date.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.