Fact-check findings
What an automated fact-checker found when it re-read SolvBTC 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.
disputed
2 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #1[disputed][awaiting moderator]in section: Security Incident: March 2026 BRO Vault Exploit ($2.7M)
“Security researchers at Verichains and Halborn noted that while the vulnerability involved callback execution via the ERC-3525/ERC-721 token standard, it was more precisely a flawed internal accounting logic rather than a canonical reentrancy attack.”
reviewerVerichains and Halborn both characterised the bug as flawed accounting logic rather than a canonical reentrancy attackHalborn says the opposite of what the page attributes to it. Olympix (also cited) likewise calls it a reentrancy bug.Proposed correction (not yet applied)Security researchers at Verichains noted that while the vulnerability resembled a re-entrancy-like attack, it was more precisely a flawed internal accounting logic rather than a canonical reentrancy attack; Halborn described it as a classic reentrancy exploit arising from the ERC-3525/ERC-721 receiver callback. - #2[disputed][awaiting moderator]in the timeline
“2026-03-06”
reviewerSolv publicly confirmed the exploit on 2026-03-06Announcement appears to be March 5, not March 6 (Invezz's article is the one dated March 6).Proposed correction (not yet applied)2026-03-05
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #5[unverifiable][awaiting moderator]in section: Security Incident: March 2026 BRO Vault Exploit ($2.7M)
“Prior to this incident, Solv Protocol had obtained security audits from Quantstamp and OpenZeppelin.”
reviewerPrior Quantstamp and OpenZeppelin auditsNot checked directly. The Halborn write-up does not mention prior audits, and I did not confirm the OpenZeppelin audit or that either audit covered the BRO contract. - #7[unverifiable][awaiting moderator]in section: TVL Manipulation Allegations (January 2025)
“DeFiLlama's reported TVL for Solv Protocol at the time stood at approximately $2.5 billion.”
reviewerDeFiLlama's reported TVL at the time was approximately $2.5 billionFigure not found in the primary cited article; other cited sources were not checked. - #8[unverifiable][awaiting moderator]in section: TVL Manipulation Allegations (January 2025)
“Solv's marketing director Eva Binari described the claims as a 'calculated smear campaign'”
reviewerEva Binari is marketing director of SolvName and title not confirmed by the article I fetched. - #11[unverifiable][awaiting moderator]in section: Overview
“As of early 2026, Solv Protocol reported over $1.7 billion in total value locked (TVL).”
reviewerOver $1.7 billion TVL, over 60% native BTC, custodians, backers, and a September 2025 Chainlink PoR integrationNot fetched. Search results confirm only the Chainlink integration (Sept 2025) in passing. TVL, backers, custodians and the 60% figure were not verified.citedsolv.finance/
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #9[partially supported][awaiting moderator]in the timeline
“Nubit co-founder Lianchuang Hans publicly alleges Solv Protocol is manipulating TVL figures by recycling BTC deposits across multiple protocols.”
reviewerTimeline date for the TVL allegation is 2025-01-03Consistent but the exact day is unconfirmed. The Jan 5 denial date is also unchecked. Timeline entries have empty source fields.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #3[confirmed][no action needed]in section: Security Incident: March 2026 BRO Vault Exploit ($2.7M)
“On March 3, 2026, the Solv Protocol BitcoinReserveOffering (BRO) vault contract suffered an exploit resulting in the theft of approximately 38.0474 SolvBTC, valued at roughly $2.7 million USD at the time.”
reviewerBRO vault exploit on March 3, 2026 of 38.0474 SolvBTC (~$2.7M), 22 iterations, 567M BRO, 1,211 WETH, contract addressCore incident facts match multiple sources. QuillAudits gives about $2.5M, a minor variance. - #4[confirmed][no action needed]in section: Security Incident: March 2026 BRO Vault Exploit ($2.7M)
“Security firms Hypernative Labs, SlowMist, and CertiK were engaged for post-incident investigation.”
reviewerSolv pledged reimbursement, offered 10% bounty, engaged Hypernative, SlowMist and CertiK; fewer than ten users affectedSupported. - #6[confirmed][no action needed]in section: TVL Manipulation Allegations (January 2025)
“In early January 2025, shortly before the SOLV token launch on January 17, 2025, Nubit co-founder Lianchuang Hans publicly alleged that Solv Protocol had been inflating its TVL figures.”
reviewerHans publicly alleged TVL inflation; a whale alleged her 1,800 BTC were used as reserves while under her control; Chow disputed; team called it a smear campaign and threatened legal actionCryptopolitan does not name Eva Binari or her role, and gives no DeFiLlama TVL figure. Those details are not checked here. - #10[confirmed][no action needed]in the timeline
“Verichains publishes technical post-mortem classifying the vulnerability as a double-mint logic flaw rather than a canonical reentrancy attack.”
reviewerVerichains published its post-mortem on 2026-03-13Supported.