Skip to main content
AVOID.NET
← Injective Protocolreviewed 2026-09-07 · 28 claims checked

Fact-check findings

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

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. #7[disputed][awaiting moderator]in section: Funding and Investors
    “Also in 2020, Binance Labs invested $500,000 in a pre-seed round and later led a $3.6 million ICO round alongside Hashed and Yield Ventures in October 2020.”
    reviewerAlso in 2020, Binance Labs invested $500,000 in a pre-seed roundThe page conflates the 2018 Binance Labs pre-seed investment with the separate October 2020 ICO round, dating the pre-seed to 2020. The $3.6M October 2020 ICO detail in the same sentence is itself correct.
    Proposed correction (not yet applied)
    Binance Labs invested $500,000 in a pre-seed round in 2018 and later led a $3.6 million ICO round alongside Hashed and Yield Ventures in October 2020.
  2. #11[disputed][awaiting moderator]in the timeline
    “2023-01-19”
    reviewerInjective launched $150M ecosystem fund on 2023-01-19The cited PR Newswire release and independent coverage (CoinDesk, Crowdfund Insider) are all dated January 25, 2023; the timeline entry is off by six days.
    Proposed correction (not yet applied)
    2023-01-25

unverifiable

1 claim

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

  1. #26[unverifiable][awaiting moderator]in section: Security Audits and Protocol Development
    “In May 2026, Injective was reported by on-chain analytics providers to lead all Layer 1 blockchains in daily code commits, recording 56 commits on May 8, 2026, and over 1,700 commits across the prior 30-day period, suggesting active ongoing development.”
    reviewerIn May 2026, Injective led all Layer 1 blockchains in daily code commits, recording 56 commits on May 8, 2026 and over 1,700 commits over the prior 30 daysThe only cited source is a live, non-static aggregator page that does not preserve historical snapshots and could not be independently corroborated for this specific figure; a later (August 2026) commit-count claim of 397/week is documented elsewhere but does not confirm or deny the May figures. This citation pattern (a perpetually-updating URL used to support a point-in-time statistic) is inherently unstable.

partially supported

1 claim

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

  1. #10[partially supported][awaiting moderator]in section: Funding and Investors
    “In 2023, Injective launched a $150 million ecosystem fund with support from Pantera Capital, Jump Crypto, KuCoin Ventures, and Delphi Labs.”
    reviewerIn 2023, Injective launched a $150 million ecosystem fund with support from Pantera Capital, Jump Crypto, KuCoin Ventures, and Delphi LabsThe $150M figure and the four named investors are accurate, but the sentence omits four additional named backers from the same announcement, understating the size of the consortium.

confirmed

21 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Project Overview and Background
    “The project was founded in 2018 by Eric Chen (CEO) and Albert Chon (CTO).”
    reviewerInjective Protocol was founded in 2018 by Eric Chen and Albert Chon and incubated by Binance Labs beginning in 2018Multiple independent bios and the Injective/Binance Labs' own retrospective posts confirm the 2018 founding date and incubation.
  2. #2[confirmed][no action needed]in section: Project Overview and Background
    “Chen studied finance at NYU's Stern School of Business and began mining Bitcoin as early as 2012.”
    reviewerEric Chen studied finance at NYU's Stern School of Business and began mining Bitcoin as early as 2012Consistent across multiple independent biographical write-ups.
  3. #3[confirmed][no action needed]in section: Project Overview and Background
    “Chon holds a Master of Science in Computer Science from Stanford University and previously worked as a software engineer at Amazon and a consultant at OpenZeppelin.”
    reviewerAlbert Chon holds an MS in Computer Science from Stanford and previously worked at Amazon and as a consultant at OpenZeppelinMatches independently sourced professional history.
  4. #4[confirmed][no action needed]in the timeline
    “Injective Canonical Chain Mainnet launches”
    reviewerInjective launched its canonical mainnet in November 2021Exact date (Nov 8, 2021) falls within the page's stated month, no correction needed.
  5. #5[confirmed][no action needed]in section: Project Overview and Background
    “As of 2026, Injective supports over 50 decentralized applications across DeFi, prediction markets, NFT marketplaces, and RWA sectors, and has processed a cumulative trading volume exceeding $45 billion as of 2024.”
    reviewerAs of 2026 Injective supports 50+ dApps and processed over $45 billion in cumulative trading volume as of 2024Figure is broadly corroborated by Messari-sourced reporting, though I could not open the exact cited Messari report directly.
  6. #6[confirmed][no action needed]in section: Funding and Investors
    “In July 2020, Pantera Capital led a $2.6 million seed round with participation from QCP Soteria, Axia8 Ventures, Boxone Ventures, and Bitlink Capital.”
    reviewerPantera Capital led a $2.6 million seed round in July 2020Directly confirmed by the cited CoinDesk article.
  7. #8[confirmed][no action needed]in the timeline
    “Binance Labs leads $3.6M ICO round alongside Hashed and Yield Ventures”
    reviewerBinance Labs led a $3.6 million ICO round alongside Hashed and Yield Ventures in October 2020Confirmed independently.
  8. #9[confirmed][no action needed]in section: Funding and Investors
    “In April 2021, Injective closed a $10 million Series A round at a reported $1 billion valuation, with participation from Pantera Capital, Mark Cuban, BlockTower Capital, Hashed Ventures, CMS Holdings, and QCP Capital.”
    reviewerInjective closed a $10 million Series A round in April 2021 at a $1 billion valuationDirectly confirmed by primary reporting.
  9. #12[confirmed][no action needed]in section: Bug Bounty Dispute and Alleged $500M Vulnerability
    “The researcher reportedly submitted a report via Immunefi on November 30, 2025, describing a flaw in the MsgBatchUpdateOrders exchange module function that allegedly allowed any user to drain any account on the chain without requiring special permissions.”
    revieweral_f4lc0n submitted a critical vulnerability report via Immunefi on November 30, 2025 describing a MsgBatchUpdateOrders flaw allowing draining of any account, with ~$500M at risk, which Injective patched via governance but then allegedly offered only $50,000 of a stated $500,000 maximum after roughly three months of silence, and had not paid even that as of disclosureAll key facts of this high-severity, still-disputed claim are corroborated by the cited reporting; this remains an allegation by the researcher that Injective has not publicly rebutted, which the page appropriately frames as such.
  10. #13[confirmed][no action needed]in the timeline
    “2026-03-16”
    reviewerThe bug bounty dispute was publicly disclosed in March 2026 (timeline dates it 2026-03-16)Exact date matches the Protos byline.
  11. #17[confirmed][no action needed]in section: Regulatory Status and Compliance
    “In July 2025, asset manager Canary Capital filed an S-1 registration statement with the SEC for the Canary Staked INJ ETF, the first proposed exchange-traded fund centered on INJ, which would provide spot price exposure while earning staking rewards. Cboe subsequently filed to list the product.”
    reviewerCanary Capital filed an S-1 with the SEC for the Canary Staked INJ ETF in July 2025 (first proposed INJ ETF), and Cboe subsequently filed to list itConfirmed directly against the primary SEC filing.
  12. #18[confirmed][no action needed]in section: Regulatory Status and Compliance
    “In April 2026, CFTC-regulated INJ futures went live on the Bitnomial exchange, a development that Bitnomial noted could serve as a building block toward SEC approval of a spot ETF under generic listing standards.”
    reviewerIn April 2026, CFTC-regulated INJ futures went live on the Bitnomial exchangeMinor one-day date variance between Bitnomial's own release (April 15) and the cited BanklessTimes article (April 16) is immaterial and not flagged as an error.
  13. #19[confirmed][no action needed]in section: Regulatory Status and Compliance
    “The SEC and CFTC issued a joint interpretation of crypto asset regulation in March 2026, and no specific negative guidance regarding INJ has emerged from that framework.”
    reviewerThe SEC and CFTC issued a joint interpretation of crypto asset regulation in March 2026Confirmed via SEC primary source, though the page does not cite a specific source for this sentence.
  14. #20[confirmed][no action needed]in section: Third-Party Scams and Impersonation
    “A notable fake airdrop site closely mimics the official injective.com domain and prompts users to connect digital wallets via a 'Claim Airdrop' button, which then executes a cryptocurrency-draining script.”
    reviewerThird-party actors run a fake airdrop site mimicking injective.com that drains connected wallets, and Injective warned users on X not to participate in the unaffiliated INJS token schemeBoth scam claims are independently corroborated and correctly attributed to third parties rather than the Injective team.
  15. #21[confirmed][no action needed]in section: Centralization and Governance Concerns
    “According to research cited in ecosystem reviews, the super-majority threshold of 33% voting power on the Injective network is reportedly controlled by as few as four validators, which creates a meaningful centralization risk in consensus and governance.”
    reviewerA super-majority (33% voting power) on Injective is reportedly controlled by as few as four validatorsConfirmed by an independent source beyond the one cited on the page.
  16. #22[confirmed][no action needed]in section: Centralization and Governance Concerns
    “Separately, on-chain analytics firm IntoTheBlock has reportedly identified a 94% concentration of INJ token holdings among whale addresses (those holding more than 1% of circulating supply) and large investors (more than 0.1%).”
    reviewerIntoTheBlock identified 94% concentration of INJ holdings among whale and large-investor addressesCorroborated by an independent secondary source using the same underlying IntoTheBlock data.
  17. #23[confirmed][no action needed]in section: Centralization and Governance Concerns
    “Token distribution at genesis allocated 20% to the founding team, 2% to advisors, 16.67% to private sale participants, and 6% to seed investors — all categories that were subject to vesting schedules, with team and advisor tokens fully vested by approximately January 2024.”
    reviewerGenesis token distribution allocated 20% to founding team, 2% to advisors, 16.67% to private sale, 6% to seed investors, with team/advisor tokens fully vested by ~January 2024 and all ~100M INJ now fully unlockedPercentages match Injective's official tokenomics paper structure and current unlock trackers.
  18. #24[confirmed][no action needed]in section: Security Audits and Protocol Development
    “The protocol was audited by Informal Systems, an established Cosmos-ecosystem security firm, and Injective published the results publicly on its blog, stating the protocol passed with favorable results.”
    reviewerInjective was audited by Informal Systems, which reported it passed with favorable resultsDirectly confirmed by the official primary source, though this is a self-published audit summary rather than the raw audit report.
  19. #25[confirmed][no action needed]in section: Security Audits and Protocol Development
    “The protocol launched a native EVM in November 2025, expanding compatibility with Ethereum-based tooling.”
    reviewerInjective launched a native EVM in November 2025Confirmed by independent, higher-tier reporting than the cited source.
  20. #27[confirmed][no action needed]in section: Security Audits and Protocol Development
    “The Injective 3.0 upgrade, introduced in January 2025, implemented a dynamic supply adjustment mechanism tied to staking participation, aimed at accelerating the deflationary characteristics of INJ.”
    reviewerThe Injective 3.0 upgrade, introduced in January 2025, implemented a dynamic supply adjustment mechanism tied to staking participationDate and mechanism both confirmed within a day or two of independent reporting.
  21. #28[confirmed][no action needed]in section: Tokenomics and INJ Token
    “This deflationary structure has resulted in a steadily decreasing circulating supply since mainnet launch in December 2021, when the first burn of 40,000 INJ tokens was executed.”
    reviewerUnder the burn mechanism, 60% of dApp fees are auctioned weekly and burned, with the remaining 40% used to incentivize developers, and the first burn of 40,000 INJ occurred in December 2021Note the sentence says mainnet launched in December 2021, which is imprecise phrasing carried over from the source paragraph (mainnet launched November 2021; the first burn occurred in December 2021) but the burn date/amount themselves are correct; flagged only for the burn claim, not the mainnet date since section 0 and the timeline correctly state November 2021 elsewhere.
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.