Skip to main content
AVOID.NET
← Fluid (Instadapp)reviewed 2026-10-16 · 12 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Fluid (Instadapp) 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

3 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. #1[disputed][awaiting moderator]in section: Protocol Overview
    “The protocol raised a total of $24.5 million from investors including Pantera Capital, Coinbase Ventures, Naval Ravikant, and Balaji Srinivasan.”
    reviewerFluid/Instadapp raised a total of $24.5 million from investors including Pantera Capital, Coinbase Ventures, Naval Ravikant, and Balaji Srinivasan.Public funding records (The Block's original seed-round report and 2021 Series A coverage, corroborated by CB Insights/AlphaGrowth totals of ~$12.4M) do not support a $24.5M total raise; the real total appears to be roughly half that figure. Same error recurs in sections[5] and timeline[2].
    Proposed correction (not yet applied)
    The protocol raised a total of approximately $12.4 million from investors including Pantera Capital, Coinbase Ventures, Naval Ravikant, and Balaji Srinivasan.
  2. #2[disputed][awaiting moderator]in section: Token Performance and Market Position
    “Fluid is backed by Pantera Capital and Coinbase Ventures, among other investors, and has raised $24.5 million in total funding.”
    reviewerFluid is backed by Pantera Capital and Coinbase Ventures, among other investors, and has raised $24.5 million in total funding.Same underlying funding-total error as sections[0]; none of the three cited sources for this section (DeFiLlama, CoinGecko, Messari) actually report a funding total at all, so the figure is unsupported by its own citations as well as by independent records.
    Proposed correction (not yet applied)
    Fluid is backed by Pantera Capital and Coinbase Ventures, among other investors, and has raised approximately $12.4 million in total funding.
  3. #3[disputed][awaiting moderator]in the timeline
    “Pantera Capital and Coinbase Ventures invest in Instadapp as part of a $24.5 million total fundraise.”
    reviewerPantera Capital and Coinbase Ventures invested in Instadapp as part of a $24.5 million total fundraise in 2021.Same funding-total error as sections[0] and sections[5]; the 2021 round itself (Series A, ~$10M) is correctly timed but the cumulative figure attached to it is wrong.
    Proposed correction (not yet applied)
    Pantera Capital and Coinbase Ventures invest in Instadapp's $10 million Series A round.

unverifiable

1 claim

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

  1. #12[unverifiable][awaiting moderator]in section: May 2026 Key Compromise: Merkle Rewards Infrastructure Breach
    “On-chain researcher YAM (@yieldsandmore) surfaced the breach on May 31, 2026, prior to any official acknowledgment.”
    reviewerOn-chain researcher YAM (@yieldsandmore) surfaced the breach on May 31, 2026, prior to any official acknowledgment, and Fluid published an official statement the same day.The claim is consistent with and repeated across multiple secondary sources (Crypto Times, Bitget) that were independently fetched, but the primary X post itself could not be accessed to verify first-hand, so the direct citation is unverifiable even though the underlying fact is well corroborated elsewhere.

partially supported

3 claims

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

  1. #4[partially supported][awaiting moderator]in section: Protocol Overview
    “It was founded in 2018 at the ETHIndia Hackathon by brothers Samyak Jain (CTO) and Sowmay Jain (CEO).”
    reviewerFluid was founded in 2018 at the ETHIndia Hackathon by brothers Samyak Jain (CTO) and Sowmay Jain (CEO).The 2018 ETHIndia founding and Sowmay-as-CEO are well corroborated across sources. Samyak's CTO title is confirmed by only one lower-tier source (Gate.com); other directories either omit a CTO title or list a different person as CPO, so the specific title claim is weaker than the founding-story claim.
  2. #6[partially supported][awaiting moderator]in section: May 2026 Key Compromise: Merkle Rewards Infrastructure Breach
    “The total estimated USD loss was approximately $215,000 based on contemporaneous token prices.”
    reviewerThe total estimated USD loss from the May 2026 key compromise was approximately $215,000.The $215,000 figure is accurate per independent secondary reporting, but none of the three sources the page actually cites for this section states a USD figure; the citation does not support the specific number asserted.
  3. #10[partially supported][awaiting moderator]in section: Token Performance and Market Position
    “As of June 2026, defillama.com reports a protocol TVL of approximately $720 million, down from a peak closer to $970 million reported around the time of the Resolv resolution in May 2026.”
    reviewerFluid operates with approximately $720 million in TVL as of mid-2026 across Ethereum, Arbitrum, Base, Plasma, and Polygon.The $720M TVL figure is roughly in line with current DeFiLlama data. However, the page's chain list (Ethereum, Arbitrum, Base, Plasma, Polygon) omits Solana, which Fluid's own Q4 2025 update and a Solana ecosystem directory list as one of its largest deployments. The reason for the large gap between DeFiLlama's current TVL and Fluid's own much larger Q4 figures is unclear and may reflect a sharp TVL decline following the two 2026 incidents, but the missing Solana chain looks like an omission rather than a resolved number.

confirmed

5 claims

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in section: May 2026 Key Compromise: Merkle Rewards Infrastructure Breach
    “On May 27, 2026, attackers compromised two operational keys within Fluid's off-chain Merkle rewards distribution infrastructure.”
    reviewerOn May 27, 2026, attackers compromised two operational keys within Fluid's off-chain Merkle rewards distribution infrastructure, draining ~125,000 FLUID and 51,900 GHO; the attacker's wallet is 0x4925120CbE5A78Bf08F26f6E8cdF820f4c1D3dfB; proceeds were laundered via Tornado Cash.Fully corroborated by the primary cited source. A competing report (coinstats/threatcluster, not cited by the page) gives smaller interim figures (112,883 FLUID/47,903 GHO from three distributors) that the page's own text also discloses as the narrower interim count, so the two are not in conflict.
  2. #7[confirmed][no action needed]in section: March 2026 Resolv Incident: Third-Party Oracle Failure and Bad Debt
    “In late March 2026, Resolv Labs' signing infrastructure was compromised by an external attacker, resulting in the malicious minting of approximately $80 million in unbacked USR stablecoin tokens.”
    reviewerIn late March 2026 (March 22), Resolv Labs' signing infrastructure was compromised, resulting in ~$80 million in unbacked USR minted and ~$25 million in extracted value; Fluid had ~$100 million exposure to USR with ~$21 million in bad debt.Core facts (date, mint size, extraction amount) are well corroborated by The Block and Halborn. Fluid's specific $21M bad-debt figure is from later reporting (DeFi Prime, Bitget, Fluid's own governance post) rather than Halborn's earlier $10M+ estimate, which is consistent with the figure settling upward as the incident resolved, not a contradiction.
  3. #8[confirmed][no action needed]in section: March 2026 Resolv Incident: Third-Party Oracle Failure and Bad Debt
    “The total bad debt was distributed as follows: Resolv Labs contributed approximately $9.7 million, Fluid's governance treasury absorbed approximately $8.2 million, and the core team agreed to cover approximately $1.5 million from future revenue.”
    reviewerThe bad debt was distributed as Resolv ~$9.7 million, Fluid governance treasury ~$8.2 million, and the core team ~$1.5 million from future revenue; the team used a pre-approved DEX Lite credit line to consolidate the bad debt before the governance vote was completed.Directly confirmed by DeFi Prime's reporting, which also corroborates the page's characterization of the controversy over using the credit line ahead of the governance vote.
  4. #9[confirmed][no action needed]in section: Smart Contract Security and Audit History
    “MixBytes published a security audit report of the Fluid Vault Protocol dated June 25, 2024.”
    reviewerFluid's smart contracts have been audited by MixBytes (June 25, 2024), Statemind (Dec 2023, Dec 2024, Oct 2025, March 2026), and OpenZeppelin (earlier Instadapp era proxy wallet/registry contracts).OpenZeppelin audit scope independently confirmed via direct fetch. MixBytes/Statemind dates could not be independently re-derived from the raw PDFs but the documents exist at the cited URLs and are not dead links.
  5. #11[confirmed][no action needed]in section: Disclosure Delay and Transparency Concerns
    “Community observers further noted that a $77 million USDC withdrawal from the protocol began on May 28, 2026 — one day after the exploit and three days before public disclosure.”
    reviewerA $77 million USDC withdrawal from Fluid began on May 28, 2026, one day after the exploit and three days before public disclosure, fueling unverified speculation about advance knowledge of the breach.Page's hedged framing ('unverified speculation,' 'Tier 3,' 'No evidence of insider trading has been formally established') matches how the underlying reporting itself characterizes the allegation.
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.