← Alephiumreviewed 2026-10-16 · 25 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Alephium 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.
- #6[disputed][awaiting moderator]in section: Attack Mechanism and Root Cause
“Three of four guardian keys were apparently leveraged in the attack, meeting the signing quorum for the forged transfers.”
reviewerThree of four guardian keys were leveraged/compromised to meet the signing quorumThis sentence re-introduces the superseded 'compromised keys' narrative within the same paragraph that otherwise correctly states the root cause was an off-chain backend vulnerability — an internal contradiction. Alephium's official postmortem explicitly rules out key compromise.Proposed correction (not yet applied)Three of the four guardians reportedly countersigned the forged messages, satisfying the signing quorum for the fraudulent transfers, without their private keys being compromised. - #7[disputed][awaiting moderator]in section: May 2026 TokenBridge Exploit — $815,000 Drained
“Approximately 500,000 of the minted wALPH tokens were sold on Uniswap before the team could act, while an additional approximately 400,000 entered liquidity pools.”
reviewerApproximately 500,000 wALPH sold on Uniswap, with an additional ~400,000 entering liquidity pools (implying ~900,000 total uncirculated)The page's own section 4 (Team Response) correctly states the remainder in circulation was 'approximately 500,000 wALPH' total, directly contradicting this sentence's implication of 500,000 + 400,000 = ~900,000. This appears to be a double-count of the same pool of tokens.Proposed correction (not yet applied)Approximately 400,000 of the minted wALPH tokens were dumped into Uniswap liquidity pools before the team could act, with a further approximately 100,000 sold from a separate address, together accounting for the roughly 500,000 wALPH that remained in circulation after the burn.
unverifiable
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #8[unverifiable][awaiting moderator]in section: Background and Overview
“It was founded in 2018 by Cheng Wang, a PhD graduate of EPFL (Ecole Polytechnique Federale de Lausanne) who previously researched distributed consensus algorithms.”
reviewerCheng Wang was a PhD graduate of EPFL who previously researched distributed consensus algorithmsNo source cited anywhere on the page, nor any independent source found, actually states Cheng Wang holds a PhD from EPFL. This appears to be an unsupported embellishment of his biography. - #9[unverifiable][awaiting moderator]in the timeline
“Cheng Wang begins building Alephium, developing the BlockFlow sharding algorithm and Proof-of-Less-Work consensus mechanism.”
reviewerCheng Wang began building Alephium in 2018The 2018 start date is plausible (Alephium's whitepaper work is widely dated to around then) but the sole cited source does not actually support it, and no independent confirmation was found. - #25[unverifiable][awaiting moderator]in section: Market Impact
“As of June 3, 2026, CoinMarketCap reported ALPH at approximately $0.034 with a market cap of approximately $4.56 million, down roughly 13% over the prior seven days, reflecting post-exploit market pressure.”
reviewerAs of June 3, 2026, CoinMarketCap reported ALPH at approximately $0.034 with a $4.56 million market cap, down ~13% over 7 daysCould not independently confirm this specific historical snapshot; the figure is plausible given the broader price range found but not verifiable from an accessible historical source.
stale
6 claimsThe claim was accurate when written but events since have overtaken it.
- #1[stale][awaiting moderator]in the summary
“On May 29-30, 2026, its TokenBridge was exploited for approximately $815,000 in approximately seven minutes via an off-chain backend vulnerability that allowed forged guardian messages to authorize unauthorized transfers and the minting of 13.76 million unbacked wrapped ALPH tokens.”
reviewerAlephium's TokenBridge was exploited for approximately $815,000 (summary)Every secondary-source article cited by the page (The Defiant, CryptoTimes, BeInCrypto, Phemex) repeats an early $815,000 estimate from May 30, 2026. Alephium's own postmortem, published months later (Sept 4, 2026) and not cited anywhere on the page, gives a materially different figure of approximately $305,000 in backed collateral withdrawn, with no reference to the earlier number. This is the single most consequential error on the page and recurs in the section heading, two section bodies, and the timeline.Proposed correction (not yet applied)On May 29-30, 2026, its TokenBridge was exploited for approximately $305,000 in approximately seven minutes via an off-chain backend vulnerability that allowed forged guardian messages to authorize unauthorized transfers and the minting of 13.76 million unbacked wrapped ALPH tokens. - #2[stale][awaiting moderator]in section: May 2026 TokenBridge Exploit — $815,000 Drained
“May 2026 TokenBridge Exploit — $815,000 Drained”
reviewerSection heading states the exploit drained $815,000Same underlying error as the summary figure; see alephium-815k-vs-305k-loss.Proposed correction (not yet applied)May 2026 TokenBridge Exploit — $305,000 Drained - #3[stale][awaiting moderator]in section: May 2026 TokenBridge Exploit — $815,000 Drained
“On May 29-30, 2026, Alephium's TokenBridge — a private fork of the Wormhole bridge protocol operating with only four guardians compared to Wormhole mainnet's nineteen — was exploited for approximately $815,000 across Ethereum and BNB Chain.”
reviewerTokenBridge exploited for approximately $815,000 across Ethereum and BNB ChainThe four-vs-nineteen guardian comparison and 'private Wormhole fork' framing are independently confirmed and are not in dispute; only the dollar figure is wrong. Notably, the page's own itemized asset breakdown later in this same section (200,967.31 USDT + 17,594.63 USDC + 5.18 WETH + 0.335 WBTC + 36,750.106 USDT + 24.386 WBNB) sums to roughly $300-335K at plausible 2026 asset prices — closer to the postmortem's $305,000 than to $815,000 — suggesting the itemized figures were always more consistent with $305K and the $815K headline total was simply wrong.Proposed correction (not yet applied)On May 29-30, 2026, Alephium's TokenBridge — a private fork of the Wormhole bridge protocol operating with only four guardians compared to Wormhole mainnet's nineteen — was exploited for approximately $305,000 across Ethereum and BNB Chain. - #4[stale][awaiting moderator]in section: Bridge Architecture Risk and Guardian Model Concerns
“The total loss of $815,000 is disproportionately large relative to Alephium's market capitalization of approximately $4.5 million at the time of the exploit.”
reviewerTotal loss of $815,000 is disproportionately large relative to market capSame underlying error; see alephium-815k-vs-305k-loss.Proposed correction (not yet applied)The total loss of $305,000 is disproportionately large relative to Alephium's market capitalization of approximately $4.5 million at the time of the exploit. - #5[stale][awaiting moderator]in the timeline
“By 09:17:59 UTC, $815,000 in assets (USDT, USDC, WETH, WBTC) is drained from Ethereum and 13,757,076 unbacked wALPH minted.”
reviewer$815,000 in assets drained from Ethereum by 09:17:59 UTCSame underlying error; see alephium-815k-vs-305k-loss. The non-dollar details in this timeline entry (timestamps, wALPH quantity) are independently confirmed and not in dispute.Proposed correction (not yet applied)By 09:17:59 UTC, $305,000 in assets (USDT, USDC, WETH, WBTC) is drained from Ethereum and 13,757,076 unbacked wALPH minted. - #13[stale][awaiting moderator]in section: Background and Overview
“As of June 2026, the circulating supply is approximately 133.3 million ALPH against a maximum supply of 1 billion ALPH, with a market capitalization of approximately $4.5 million USD.”
reviewerAs of June 2026, Alephium's maximum supply is 1 billion ALPHThe 1-billion-cap figure was accurate under Alephium's original design but was officially removed over a year before the date the page purports to describe.Proposed correction (not yet applied)As of June 2026, the circulating supply is approximately 133.3 million ALPH; following the July 2025 Danube upgrade, ALPH emissions are uncapped and there is no fixed maximum supply, with a market capitalization of approximately $4.5 million USD.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #10[partially supported][awaiting moderator]in section: Background and Overview
“A pre-sale funding round of $3.6 million was completed in October 2021, with investors including Alphemy Capital and White Paper Capital.”
reviewerPre-sale funding round of $3.6 million with Alphemy Capital and White Paper Capital, completed October 2021Amount and investor names are independently corroborated. The precise closing date could not be verified because the only source for it (Messari) is behind a login wall, and the earliest independent coverage found predates the claimed close by about four weeks. - #11[partially supported][awaiting moderator]in the timeline
“Alephium closes a $3.6 million pre-sale funding round with investors including Alphemy Capital and White Paper Capital.”
reviewerPre-sale closed on 2021-10-06Same issue as the sections[0] pre-sale finding; see alephium-presale-date-unverified. - #12[partially supported][awaiting moderator]in the timeline
“Network hashrate reaches six-month projections within 48 hours.”
reviewerNetwork hashrate reached six-month projections within 48 hours of mainnet launchThe mainnet launch date itself is well supported; this specific hashrate/projection detail is not found in the cited source or in any other source checked, and appears to be an unsupported addition.
confirmed
11 claimsThe cited evidence supports the claim as written.
- #14[confirmed][no action needed]in section: Background and Overview
“The mainnet launched on November 8, 2021.”
reviewerAlephium mainnet launched November 8, 2021Independently confirmed by Alephium's own materials. - #15[confirmed][no action needed]in section: May 2026 TokenBridge Exploit — $815,000 Drained
“The attack was detected by blockchain security firm Blockaid.”
reviewerExploit was detected by blockchain security firm BlockaidConsistently confirmed across multiple sources. - #16[confirmed][no action needed]in section: May 2026 TokenBridge Exploit — $815,000 Drained
“The attacker completed the primary drain in approximately 64 seconds on Ethereum and then moved to BNB Chain within three seconds of completing the Ethereum leg, with the entire operation concluding in roughly seven minutes.”
reviewerAttack completed in ~64 seconds on Ethereum, moved to BNB Chain within 3 seconds, total ~7 minutesMatches the detailed timestamp breakdown in the cited post-mortem coverage, consistent with timeline[3]. - #17[confirmed][no action needed]in section: May 2026 TokenBridge Exploit — $815,000 Drained
“In addition to draining locked assets, the attacker minted 13,757,076.37 wrapped ALPH (wALPH) tokens on Ethereum without any corresponding ALPH being locked on the Alephium chain — a quantity that exceeded Alephium's entire prior Ethereum-side circulating wALPH supply.”
reviewer13.76 million wALPH minted, exceeding Alephium's entire prior Ethereum-side circulating wALPH supplyQuantity confirmed by both press coverage and the official postmortem. - #18[confirmed][no action needed]in section: May 2026 TokenBridge Exploit — $815,000 Drained
“Proceeds from stolen assets were reported to have been partially routed through Tornado Cash for obfuscation.”
reviewerProceeds were partially routed through Tornado Cash for obfuscationConfirmed, though strongly understated by the word 'partially' — the official reporting indicates the large majority of liquidated ETH proceeds were mixed, not merely 'partially' routed. None of the five sources actually cited for this section mention Tornado Cash directly; the claim is corroborated only via Alephium's own later reports. - #19[confirmed][no action needed]in section: Attack Mechanism and Root Cause
“Initial reporting attributed the exploit to compromised guardian private keys, but subsequent analysis by Blockaid and Alephium's own post-mortem traced the root cause to an off-chain vulnerability in the bridge backend.”
reviewerRoot cause was an off-chain backend vulnerability, not compromised guardian keysStrongly confirmed by the official postmortem. Note this directly conflicts with the later sentence in the same section claiming guardian keys were 'leveraged' (see alephium-guardian-key-compromise-claim). - #20[confirmed][no action needed]in section: Attack Mechanism and Root Cause
“The bridge used a reduced guardian set of four operators (identified as Swiss entities Bity and Alt, and community operator NoTrustVerify), with a quorum threshold of three required.”
reviewerBridge used a reduced guardian set of four operators (Bity, Alt, NoTrustVerify) with a quorum threshold of threeGuardian identities and quorum both corroborated. - #21[confirmed][no action needed]in section: Team Response and Recovery Actions
“A total of 13,257,077.37295 wALPH was destroyed, representing approximately 96.4% of the fraudulently minted supply.”
reviewer13,257,077.37295 wALPH burned, representing ~96.4% of fraudulently minted supplyPrecise figures match the official source exactly. - #22[confirmed][no action needed]in section: Team Response and Recovery Actions
“The remaining approximately 500,000 wALPH that had already entered market trading remained in circulation; Alephium committed to injecting native ALPH to fully back those tokens and prevent losses to secondary holders.”
reviewerRemaining ~500,000 wALPH stayed in circulation; Alephium committed to backing it with native ALPHCorrectly matches both the amount (500,000, not 500,000+400,000 as stated elsewhere) and the compensation commitment. - #23[confirmed][no action needed]in section: Regulatory and Legal History
“No regulatory actions, SEC or CFTC enforcement proceedings, or legal filings involving Alephium or its founders were identified in publicly available records as of the investigation date.”
reviewerNo regulatory actions, SEC/CFTC proceedings, or legal filings involving Alephium were identifiedA negative claim with no independent evidence found to contradict it; however, this section cites no sources at all, which is a sourcing gap even though the conclusion holds up on an independent search. - #24[confirmed][no action needed]in section: Market Impact
“At the time of the exploit on May 30, 2026, ALPH was trading in the range of approximately $0.036 to $0.041 with a market capitalization below $6 million.”
reviewerALPH traded $0.036-$0.041 with market cap below $6 million at the time of the exploitBroadly consistent with multiple independent price trackers, though exact historical snapshots vary by source and none pins down May 30 specifically.
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.