← RISExreviewed 2026-09-07 · 16 claims checked
Fact-check findings
What an automated fact-checker found when it re-read RISEx 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
4 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #9[disputed][awaiting moderator]in section: Team and Backing
“RISE Chain raised $8 million in funding from investors including Galaxy Ventures, Vitalik Buterin (Ethereum co-founder), Finality Capital Partners, EtherFi, OrangeDAO, DACM, P2 Ventures, and Stani Kulechov (Aave founder). An earlier $3.2 million seed round in September 2024 included Sam Kazemian and Anthony Sassano.”
reviewerRISE Chain raised $8 million in funding from a single group of investors — Galaxy Ventures, Vitalik Buterin, Finality Capital Partners, EtherFi, OrangeDAO, DACM, P2 Ventures, and Stani Kulechov — with a separate, earlier $3.2M seed round in September 2024 involving Sam Kazemian and Anthony Sassano.The page merges two separate funding rounds into one sentence and misattributes seed-round backers (Vitalik Buterin, Stani Kulechov, Finality Capital Partners, EtherFi, OrangeDAO, DACM, P2 Ventures) to the later $8M-cumulative/Galaxy round, while adding Sam Kazemian to the seed round, whose name does not appear in any primary coverage of that round found.Proposed correction (not yet applied)RISE Chain raised $8 million in cumulative funding, most recently a $4 million round backed by Galaxy Ventures. An earlier $3.2 million seed round in September 2024 included Vitalik Buterin (Ethereum co-founder), Stani Kulechov (Aave founder), Finality Capital Partners, EtherFi, OrangeDAO, DACM, P2 Ventures, and Anthony Sassano. - #10[disputed][awaiting moderator]in the timeline
“Rise Labs closes a $3.2 million seed round including Vitalik Buterin, Sam Kazemian, and Anthony Sassano.”
reviewerThe September 2024 seed round included Vitalik Buterin, Sam Kazemian, and Anthony Sassano.Same underlying error as the Team and Backing section: Sam Kazemian appears to be a fabricated/unsupported addition to the seed-round investor list.Proposed correction (not yet applied)Rise Labs closes a $3.2 million seed round led by Finality Capital Partners, including angel investors Vitalik Buterin, Stani Kulechov, and Anthony Sassano. - #11[disputed][awaiting moderator]in the timeline
“RISE Chain raises $8 million in a second round led by Galaxy Ventures, with participation from Finality Capital Partners, EtherFi, OrangeDAO, and others.”
reviewerRISE Chain's second funding round raised $8 million, led by Galaxy Ventures with participation from Finality Capital Partners, EtherFi, and OrangeDAO.Conflates the $4M second-round amount with the $8M cumulative total and re-attributes seed-round VCs to the second round; same underlying mixup as the Team and Backing section and the 2024-09 timeline entry.Proposed correction (not yet applied)RISE Chain raises $4 million in a second round led by Galaxy Ventures, bringing its cumulative funding to $8 million. - #12[disputed][awaiting moderator]in the timeline
“2026-07-24”
reviewerRISEx's 'Ignite' Season 1 points program launched on July 24, 2026.The cited source's own text distinguishes the program's live-since date (July 20) from the article's publish date (July 24); the timeline entry uses the latter.Proposed correction (not yet applied)2026-07-20
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #7[unverifiable][awaiting moderator]in section: Incident Overview
“The team reported detecting the issue within minutes of occurrence, deploying a patch by 08:09 UTC on the same day. RISEx engaged SEAL 911, a 24/7 blockchain emergency security response service, and stated it was attempting to contact the address involved to negotiate a return of funds.”
reviewerRISEx engaged SEAL 911 and attempted to contact the exploiter's address to negotiate a return of funds.The claim is plausible and the described service is real, but the specific engagement and precise patch timestamp rest solely on the company's own unarchived social-media disclosure, which could not be independently fetched (blocked by platform) or corroborated elsewhere. - #16[unverifiable][awaiting moderator]in section: Root Cause: Smart-Contract Misconfiguration
“The amount drained — 673,011.56 USDC — fell below the platform's withdrawal throttling thresholds, which the team acknowledged meant existing safeguards did not trigger an alert or block the withdrawal.”
reviewerThe drained amount fell below the platform's withdrawal throttling thresholds, so existing safeguards did not trigger.This technical detail traces solely to the company's own X disclosure, which could not be fetched directly (platform blocked automated access) or corroborated in any independent write-up found.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Root Cause: Smart-Contract Misconfiguration
“An independent review by PerpFinder, published July 23, 2026, noted that DefiLlama's protocol metadata recorded zero completed audits for RISEx and assigned a security rating of 3.5 out of 10 for the platform.”
reviewerPerpFinder's review, published July 23, 2026, found zero completed audits in DefiLlama metadata and assigned RISEx a 3.5/10 security rating.The rating and audit-gap content are well supported; the specific July 23, 2026 publish date could not be independently confirmed against the source, which reads as a living page rather than a dated report.
confirmed
9 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Incident Overview
“On August 3, 2026 at approximately 07:21 UTC, an unauthorized withdrawal of 673,011.56 USDC occurred from the RWA strategy connected to RISEx's XLP vault.”
reviewerAn unauthorized withdrawal of 673,011.56 USDC occurred from RISEx's XLP vault RWA strategy on August 3, 2026 at approximately 07:21 UTC.Core amount and date are corroborated by an independent aggregator (DefiLlama) in addition to the company's own disclosure, so this is well supported despite the primary source being a company X post. - #2[confirmed][no action needed]in section: Root Cause: Smart-Contract Misconfiguration
“The misconfigured contract was deployed on July 13, 2026, and remained live and exploitable for 21 days without detection.”
reviewerThe misconfigured RWA strategy contract was deployed July 13, 2026 and remained exploitable for 21 days before detection.Deployment date and window are consistent with the pre-exploit PerpFinder review timeline; July 13 to August 3 is 21 days, arithmetic checks out. - #3[confirmed][no action needed]in section: Root Cause: Smart-Contract Misconfiguration
“No third-party audit had been completed or published for RISEx at the time of the exploit.”
reviewerNo third-party audit had been completed or published for RISEx at the time of the exploit.Directly confirmed by the cited primary source's own language. - #5[confirmed][no action needed]in section: Depositor Compensation
“RISEx compensated all XLP vault depositors in full using a portion of the fees generated by the RISEx protocol during July 2026.”
reviewerRISEx compensated all XLP vault depositors in full from July 2026 protocol fees, and the stolen USDC itself was not recovered.Corroborated by a secondary incident tracker in addition to the company statement. - #6[confirmed][no action needed]in section: Depositor Compensation
“There is no publicly available postmortem with a detailed technical breakdown of the misconfiguration as of the time of this investigation.”
reviewerThere is no publicly available postmortem with a detailed technical breakdown of the misconfiguration.Absence-of-evidence claim; reasonable diligence found nothing contradicting it. - #8[confirmed][no action needed]in section: Team and Backing
“Co-founders include Sam Battenally (CEO), Sasha Mai Herbert (CGO), and Hai Nguyen (CTO).”
reviewerRISEx co-founders are Sam Battenally (CEO), Sasha Mai Herbert (CGO), and Hai Nguyen (CTO).Names and roles check out against independent coverage. - #13[confirmed][no action needed]in the timeline
“RISE Chain announces RISEx and MarketCore, positioning as a global on-chain markets infrastructure on Ethereum Layer 2.”
reviewerRISE unveiled RISEx and MarketCore as global on-chain markets infrastructure on Ethereum Layer 2, per CoinDesk coverage dated November 12, 2025.Content and date are corroborated across multiple independent outlets. - #14[confirmed][no action needed]in the timeline
“RISEx launches the 'Ignite' Season 1 public points and rewards program following $3 billion in cumulative trading volume.”
reviewerRISEx's early access phase generated over $3 billion in cumulative trading volume before the Ignite Season 1 launch.Figure is consistently reported across multiple outlets syndicating the same underlying press release. - #15[confirmed][no action needed]in section: Root Cause: Smart-Contract Misconfiguration
“The team's own FAQ, as of July 2026, stated that contracts had undergone only internal reviews and were 'in the process of third-party audits,' with no firm, scope, or timeline named.”
reviewerRISEx's FAQ states contracts underwent internal review only and third-party audits were in progress with no firm, scope, or timeline named.Direct, verbatim-level match to the cited primary source.
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.