Solv Protocol (SolvBTC)

The research on SolvBTC remains unresolved. Plain SolvBTC is a 1:1 reserve representation of Bitcoin and does not itself pay the opaque 3-8% strategy yield described by the earlier draft. Yield comes from separate products layered on top. SolvBTC still replaces native BTC with governed minting, custodial or threshold-signing, cross-chain, contract and scheduled-redemption dependencies. Those controls matter whether or not the token itself pays a return. The 2026-03-05 incident affected a Bitcoin Reserve Offering wrapper vault rather than the core SolvBTC token contract; Solv said fewer than ten users were affected and committed to cover losses. Current docs describe a redesigned FROST-based Bitcoin architecture and a separate on-chain Safe Vault, but a fund manager processes ordinary redemptions weekly after tokens are burned. Keep the assessment unresolved until mint and redemption controls have a clean operating interval and current reserve and authority maps can be reproduced independently. A client benefit over self-custodied BTC is a later client-purpose question, not a research hurdle.

Review triggers: events that reopen the verdict
• Any unauthorized mint, reserve deficit, redemption suspension or unreconciled cross-chain supply difference
• Any BRO-incident loss remains unreimbursed or an authorized wrapper retains the same unremediated incident weakness
• Any chain, reserve asset, signer set, vault or upgrade authority is absent from the current reserve-control map
• A proposed-size native-BTC redemption misses one published weekly processing cycle

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-05.

The research file

Mechanism and scope

SolvBTC is intended to represent one unit of Bitcoin reserve across supported chains. Users deposit native BTC or accepted wrapped Bitcoin through guarded vaults; a multisignature or authorized router then mints SolvBTC. Current architecture documents split Bitcoin-mainnet custody from on-chain liquidity: a FROST threshold-signing network controls native BTC execution, while deposit, whitelisted swap, standard redemption and Safe Vault contracts serve EVM use.

SolvBTC is the reserve token, not the yield strategy. Yield-bearing Solv products mint separate receipts and deploy reserves into staking, lending or liquidity strategies. Combining those products under one headline APY obscures which token, manager, strategy and redemption schedule the client actually owns.

Control, custody and reserves

The reserve documents claim real-time 1:1 proof of reserve and define governance powers over eligible reserve assets, mint caps, native minting chains, cross-chain rate limits and future reserve classifications. Those are real managed controls, not Bitcoin consensus rules. The mainnet design says FROST signing shares prevent reconstruction of one private key, but redemption still passes through indexing, policy approval and threshold execution.

The on-chain design adds Auditors-based governance, authorized contracts and a Safe Vault. Approval requires current participant identities, thresholds, upgrade admins, chain supply, reserve assets and encumbrances to reconcile to one machine-readable report. A proof-of-reserve total alone cannot show that every reserve is unencumbered or immediately available to ordinary redeemers.

Incident record

On 2026-03-05 Solv reported an incident involving a Bitcoin Reserve Offering vault, said fewer than ten users were affected and committed to cover losses. Solv did not describe the event as a compromise of the core SolvBTC token contract. It still matters to this decision because a peripheral reserve-offering component failed inside the SolvBTC system. The next review must identify the affected contract, remediation, reserve accounting, reimbursement completion and whether every other authorized reserve-offering contract was reviewed for the same weakness.

Exit and liquidity

The standard EVM flow burns SolvBTC immediately and issues a non-transferable redemption SFT. A fund manager, overseen by the Vault Guardian, later allocates the reserve asset to that claim. Current user docs say requests may be submitted any day but are processed the next Monday, shifted for holidays. Direct BTC redemption also requires indexer assembly, policy approval, FROST signing and Bitcoin settlement.

A market sale may be faster but adds venue depth and peg risk. Burning before allocation leaves the client holding a process claim rather than freely transferable SolvBTC. Approval would require proposed-size tests of both standard redemption and secondary sale, with elapsed time, realized asset, fees and cancellation rights recorded separately on each chain.

Comparison and assessment

Against self-custodied BTC, SolvBTC adds programmability but also reserve custody, mint authorization, smart contracts, cross-chain supply accounting and a managed redemption queue. Against a single-custodian wrapper, threshold signing and diversified reserve rules may reduce one-key concentration, but the operating system is more complex and this review has not yet reproduced its current participant map independently. Yield products must be compared separately with their actual strategy peers.

The added control and exit layers remain unresolved research questions. The recent BRO exploit strengthens the need for a clean operating interval but is not described incorrectly as a core-token exploit. No client selection is made here.

Observable reopening conditions

Resolve the file only if no further unauthorized mint, reserve shortfall or redemption impairment occurs; all BRO-incident users are documented as made whole; every authorized wrapper and vault is mapped to its current implementation and audit; and chain supply equals eligible, unencumbered reserves. Require a proposed-size native-BTC redemption inside one published processing cycle.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Solv docs — SolvBTC reserve token · primary · accessed 2026-08-14
  Supports: 1:1 reserve representation, plain SolvBTC scope
• Solv docs — reserve and governance design · primary · accessed 2026-08-14
  Supports: proof of reserve, reserve tiers, governance parameters
• Solv docs — minting and redemption · primary · accessed 2026-08-14
  Supports: Vault Guardian, redemption SFT, weekly processing
• Solv docs — current technical architecture · primary · accessed 2026-08-14
  Supports: FROST signing, Safe Vault, authorized contracts, Auditors governance
• Solv Protocol — incident statement, 2026-03-05 · primary · accessed 2026-08-14
  Supports: BRO vault incident, affected users, loss coverage commitment
• Solv Finance — public contract and audit repositories · primary · accessed 2026-08-14
  Supports: SolvBTC source code, audit repository, implementation history

Inherited controls

The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.