Solv Protocol said on September 30 that a public dispute over a blocked redemption is an individual risk review, not a freeze of its BTC+ product, and that the assets at issue, roughly 50 BTC, remain held within the protocol.
The fight went public when an X user posting as Neil Lee described depositing about 50 BTC into SolvBTC and BTC+ in July and being unable to redeem since. Solv responded that BTC+ subscriptions and redemptions are operating normally and that the case is a single transaction that triggered a risk review. It said the assets remain “fully preserved within the protocol” and have not been transferred, destroyed or otherwise disposed of.
Solv said it will decide the case on verifiable information and evidence rather than social-media claims, and that it may involve legal counsel or courts if further verification is needed. It also said it will stop answering other public threads built on online identities, effectively closing the public channel on this case.
The user’s timeline
The account behind the dispute says it withdrew about 50 BTC from Binance on July 8, 2026, converted the coins into SolvBTC and BTC+ for a stated yield near 3%, and then found mint and redeem paused. Solv disclosed a security incident on July 22 involving its BTC+ contract on BNB Smart Chain, in which a leaked deployer private key let an attacker upgrade the minting proxy and mint unauthorized tokens. The team isolated the malicious contract within three hours, froze or burned the unauthorized tokens, and restored functions on July 31, but the user’s address stayed restricted.
The user says he sent source-of-funds and wallet-control documents over weeks of Discord, Telegram and email, roughly 60 emails in total, without resolution. Solv has not published a timeline for completing the review or the specific rule the transaction allegedly tripped.
Solv’s own messaging after the July incident emphasized that BTC+ has never established official liquidity pools on any DEX and that users should only obtain the token through official channels, a warning that itself reflects how the exploit unfolded. The protocol rotated all affected credentials, upgraded deployer security and commissioned an external re-audit, and it promised a detailed post-mortem that has not yet been published in full. The September 30 statement is consistent with that pattern: controlled, legalistic and silent on the specifics of the one case everyone is watching.
Why the structure matters
BTC+ is Solv’s Bitcoin yield vault. Depositors receive a receipt token, and redemptions are not instant on every chain. Solv’s documentation sets a three-window monthly calendar for EVM redemptions, and instant redemption on BNB Chain is capped at 0.5 BTC per day protocol-wide, 0.1 BTC per trade, with a 0.25% fee. Those caps mean even normal redemptions queue, and a user expecting same-day exit can wait weeks under the standard calendar.
The deeper issue is procedural. A protocol that can pause an individual address after a security incident, without a published review rule or external adjudication, leaves users with no independent check on the decision. Solv’s position is that risk controls protect the pool; the user’s position is that two months of compliance with document requests should have produced a resolution. Neither side has published a contract event that settles the point.
It is also not the first public dispute over Solv’s reserves. In January 2025 a co-founder of Nubit alleged Solv was counting the same Bitcoin across multiple protocols and manipulating its figures on DefiLlama. Solv’s co-founder Ryan Chow rejected the allegations, said the transfer cited as evidence belonged to a different product, and threatened legal action. No third-party adjudication followed, and the entity behind the protocol is Solv Protocol Limited, registered in Gibraltar and regulated there as a credit institution and DLT institution, a jurisdiction with a limited public enforcement record in crypto disputes.
Until Solv releases the wallet, the review rule and a processed redemption, or a court filing does, the 50 BTC figure and the “assets fully preserved” statement sit next to each other as competing claims.
The lesson for depositors
The practical lesson goes beyond Solv. Yield vaults across the industry reserve the right to pause minting, redemptions or individual addresses under risk-review language buried in documentation, and the July incident showed how quickly that power gets exercised: the attack happened July 13, the disclosure came nine days later, and normal operations resumed only after an external re-audit was commissioned. Users who need guaranteed exit windows should treat products with discretionary pause powers as term deposits in practice, whatever the marketing says about liquidity, and should check whether the redemption calendar, caps and review procedures are published before depositing rather than after a dispute starts.
Yield near 3% on Bitcoin is modest by vault standards, which is part of what makes the case resonate. A depositor took a conservative product, documented his funds, and still spent a summer unable to exit. That outcome is not unique to Solv, but it is the clearest recent illustration of the gap between on-chain liquidity promises and administrative reality.
The episode also lands at a sensitive moment for Bitcoin yield products generally. Institutional Bitcoin custody has expanded rapidly this year, with Circle minting cirBTC against deposited Bitcoin for its borrowing service and major custodians adding staking and governance support for proof-of-stake assets. As more BTC gets wrapped into yield-bearing structures, the number of points where a key leak, a bad upgrade or a discretionary freeze can trap user funds grows with it. Solv’s July exploit was contained, and the protocol deserves credit for the three-hour response. The open question is whether its risk-review process will ever be transparent enough for depositors to evaluate it the way they can now evaluate the contracts.