Skip to main content
AVOID.NET
← GeniusAIreviewed 2026-11-02 · 7 claims checked

Fact-check findings

What an automated fact-checker found when it re-read GeniusAI 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

1 claim

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #2[disputed][awaiting moderator]in section: Compensation Plan and New Token Launch
    “This plan was estimated by CertiK to cover approximately 80% of identified losses.”
    reviewerCertiK estimated the remediation plan covers about 80% of losses.The 80% coverage figure is the project's goal, not a CertiK estimate.
    Proposed correction (not yet applied)
    This plan was stated by GNUS.AI to aim to cover at least 80% of identified losses.

unverifiable

2 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #3[unverifiable][awaiting moderator]in section: Compensation Plan and New Token Launch
    “The team also launched a white-hat bounty equal to 10% of stolen funds to incentivize recovery.”
    reviewerTeam launched a white-hat bounty of 10%, a $1 per token repurchase, and buyback-and-burn.Two of three cited sources do not contain this; the third (cryptorank) was not fetched. The $1 repurchase and bounty are likewise not found.
  2. #5[unverifiable][awaiting moderator]in section: ZachXBT Flag
    “ZachXBT, a pseudonymous blockchain investigator recognized for uncovering crypto fraud, scams, and exploits, flagged GeniusAI as a concern.”
    reviewerZachXBT flagged GeniusAI as a concern.None of the cited sources was shown to name GNUS.AI; the flag itself is undocumented, and the page admits the basis is vague. The summary repeats it.

stale

1 claim

The claim was accurate when written but events since have overtaken it.

  1. #7[stale][awaiting moderator]in section: Token Price Collapse
    “Current prices hover in a range of $0.34 to $0.48 depending on the source.”
    reviewerCurrent prices range from $0.34 to $0.48.Volatile price data is out of date; I have no verified replacement to propose, so no correction is given.

partially supported

1 claim

The cited evidence supports part of the claim but not all of it.

  1. #4[partially supported][awaiting moderator]in section: Compensation Plan and New Token Launch
    “and an additional $500,000 in locked fees not available until February 2025.”
    reviewerLocked fees unavailable until February 2025.The $500k locked fees are confirmed; the February 2025 date was not found in the sources I read.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: May 2024 Discord Hack and Token Exploit
    “On May 5, 2024, GNUS.AI suffered a $1.27 million exploit that security firm CertiK estimated at approximately $1.25 million.”
    reviewerA $1.27 million exploit occurred on May 5, 2024 via Discord breach, minting 100 million counterfeit GNUS.Core exploit facts corroborated by two sources.
  2. #6[confirmed][no action needed]in section: Token Price Collapse
    “CoinGecko records an all-time high of $45.26”
    reviewerCoinGecko records an ATH of $45.26.Current price on CoinGecko was about $0.89, outside the page's stated $0.34 to $0.48 range.
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.