Fact-check findings
What an automated fact-checker found when it re-read Raga Finance against the sources the page cites. Only the most recent review is shown.
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.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #5[unverifiable][awaiting moderator]in the summary
“The protocol has been flagged by ZachXBT”
reviewerRaga Finance has been flagged by ZachXBTA search for Raga Finance with ZachXBT returned nothing linking them. The page itself concedes the basis could not be verified, yet the summary states the flag as fact. The cited sources are a generic channel page and a biography. - #6[unverifiable][awaiting moderator]in section: ZachXBT Flag
“Raga Finance has been flagged by ZachXBT, the pseudonymous on-chain investigator known for documenting exploits, scams, and protocol failures across the crypto ecosystem.”
reviewerRaga Finance has been flagged by ZachXBT (section text)No evidence found of any ZachXBT flag. The section's own hedge ('low-confidence') admits this. - #9[unverifiable][awaiting moderator]in the timeline
“QuillAudits publishes a case study documenting the results of the Raga Finance Berachain smart contract audit”
reviewerQuillAudits published the case study in June 2025No date was found for the case study. The timeline entry has an empty source field. The page also says the audit predated a Feb 2025 vault launch, which conflicts with a June 2025 publication, though a later write-up is plausible. - #10[unverifiable][awaiting moderator]in section: Protocol Overview
“The protocol was originally founded in September 2023 under the name Nexus Network before rebranding to Raga Finance.”
reviewerFounded Sept 2023 as Nexus Network, rebranded to Raga Finance, CEO Mayank Raj with IIM-A MBA and prior roles at Persistence Labs and KPMG IndiaBackground claims rest on a Medium interview and LinkedIn that I did not read. The timeline's 2024-01 rebrand date is likewise unsourced.
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Protocol Logic Incident — Smart Contract Vulnerabilities
“The Raga Finance team reportedly implemented all recommended fixes prior to public launch.”
reviewerThe team fixed all findings before public launchThe page hedges with 'reportedly', which is appropriate. The fix claim comes only from the auditor, and the timing relative to launch is unsourced. - #4[partially supported][awaiting moderator]in section: Protocol Logic Incident — Smart Contract Vulnerabilities
“An independent audit was also conducted by a researcher identified as Tejas.”
reviewerAn independent audit was done by a researcher identified as TejasThe audit exists. The researcher's name rests only on a filename. - #7[partially supported][awaiting moderator]in the timeline
“Raga Finance makes a $1,000,000 seed investment in Bloctopus (formerly LZero), an infrastructure project, alongside Hivemind and the Ethereum Foundation.”
reviewerRaga invested $1M in Bloctopus (formerly LZero) in April 2025 alongside Hivemind and the Ethereum FoundationAggregators show Raga in a $1M Bloctopus seed round. The $1M is the round size, not Raga's own cheque. Dates differ (PitchBook Jan 2025, CoinCarp Apr 2025), and the Ethereum Foundation listing is unverified. - #8[partially supported][awaiting moderator]in section: Team and Corporate Background
“is an outbound investment of $1,000,000 into Bloctopus (formerly LZero)”
reviewerRaga's single tracked investment is an outbound $1,000,000 investment into BloctopusThe cited aggregators were unreadable (403 or dead host). Other aggregators show $1M as the round total, not Raga's own amount.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Protocol Logic Incident — Smart Contract Vulnerabilities
“completed over approximately six days by two auditors — uncovered 16 vulnerabilities prior to mainnet deployment”
reviewerQuillAudits found 16 vulnerabilities in Raga's Berachain contracts over about six days with two auditorsMatches the case study. The 'prior to mainnet deployment' wording is the page's inference, since the case study states no date. - #2[confirmed][no action needed]in section: Protocol Logic Incident — Smart Contract Vulnerabilities
“Missing Access Control on setVault(): the setVault() function lacked any authorization check”
reviewersetVault() lacked access control, panic() was inoperable due to modifier conflict, fee re-staking, dust-attack mint DoS, and swap formula error were foundThe case study confirms these findings. Items 2-4 (idle balances, withdrawAll fees, totalAssets) were not in the excerpt returned, so they were not individually checked. - #11[confirmed][no action needed]in section: Audit Status and Remediation
“The presence of four distinct audits across two chains is a positive indicator of security diligence.”
reviewerFour audits across two chains exist (two Berachain, two Hyperliquid)The count matches. Two of the four have no named auditor.