Solv Basis Trading

Solv Basis Trading is a set of basis-trading yield products built on top of the broader Solv Protocol BTC yield layer, not a standalone forked AMM or lending market. Identification

• Name: Solv Basis Trading (basis-trading product line within Solv Protocol).
• Website: solv.finance (via independent aggregators; protocol site claims). • All protocol-site information is an *unverified marketing claim* by design.
• Docs: Hosted under Solv Protocol documentation (e.g., sections on SolvBTC LST lineup and SAL basis trading).
• Category: BTC yield / basis-trading CeDeFi/DeFi strategies (delta‑neutral basis trades, funding-rate capture, hedging).
• Launch date (basis trading as a strategy): Solv reports a GMX-based CeDeFi basis strategy running “since August 2023”; this date is an *unverified marketing claim*.
• Chains (for solv-basis-trading pools as per aggregators): • BSC, Ethereum, Bob, Arbitrum, Mantle. Other data platforms list additional chains (Polygon, Solana, Soneium), but those refer to Solv Protocol generally, not specifically the solv-basis-trading slug, so chain coverage outside the five listed above is not clearly attributable to this product line.
• Native token: Solv Protocol uses SOLV as its native token; Solv Basis Trading itself does not have a distinct token. Main contract addresses & verification status
• SolvBTC and related LSTs (e.g., SolvBTC, SolvBTC.ENA, xSolvBTC) have documented contract addresses on Arbitrum and other chains in Solv docs, with dates for deployment.
• However, for the specific “solv-basis-trading” pools and vaults, independent contract-address mapping per chain is not verifiable as of 2026‑09‑04: aggregators list pools by name and chain (e.g., WBTC on Arbitrum, USDT on Mantle) but do not consistently expose underlying contract addresses, and explorer cross-checks are not available within this environment.
• Explorer verification status for those precise basis-trading vaults is therefore Not verifiable as of 2026‑09‑04. Fork lineage & modifications
• Available sources describe Solv Basis Trading as proprietary basis/beta‑neutral strategies built within Solv’s Staking Abstraction Layer (SAL) and integrated with external protocols (Ethena, GMX, DeFi credit markets, RWAs).
• No independent source identifies Solv Basis Trading as a fork of a specific upstream protocol (e.g., GMX, Ethena, or other basis AMMs), and no fork lineage is documented.
• Changes vs. any hypothetical upstream codebase, the presence of audits specific to the basis-trading vault contracts, and any malicious-modification history in similar forks are Not verifiable as of 2026‑09‑04. Contradiction callout > Different aggregators disagree on chain coverage and TVL attribution: some list 5 chains (BSC, Ethereum, Bob, Arbitrum, Mantle) for Solv Basis Trading, while others discuss up to 8 chains led by Polygon and Solana for the broader Solv ecosystem. The mismatch between product‑specific and protocol‑wide data is itself a risk finding (unclear scoping and labeling).

Solv Basis Trading appears to have a real product portal, not just a marketing landing page: the protocol page is an app-style dashboard with live APY presentation, and the source snippet explicitly says machine-readable data is available via a public API. That said, website maturity is only partially verifiable from the available evidence: live deposit/withdrawal flows, docs completeness, and broken-link/template checks are Not verifiable as of 2026-09-04. The strongest positive signal is the presence of a dedicated application page plus an explicit public API claim.

A separate protocol listing also points users to Solv’s official site and shows that the project is being tracked as a live DeFi protocol rather than a static brochure. However, the product functionality observable from the available sources is limited to this listing-level evidence, so confirmation of actual deposit/withdrawal operability is Not verifiable as of 2026-09-04. Open API: yes, a public API is claimed on the protocol page.

Whether it is fully documented, rate-limited, or intended for broad external use is Not verifiable as of 2026-09-04. No reliable evidence of fake metrics, template-site artifacts, or broken links was available in the retrieved sources, so those remain Not verifiable as of 2026-09-04.

Solv Protocol has an active bug bounty program on Immunefi. The program is focused on smart contracts and aims to prevent loss of staked principal, theft or freezing of unclaimed yield, and failure to deliver promised returns. Reported reward tiers are Critical $50,000, High $25,000, Medium $10,000, and Low $3,000; critical/high reports must include a PoC and fix suggestion.

Payouts are handled by the Solv team and paid in USDT. A separate 2026 HackenProof program for Solv smart contracts also appears active, with a stated range of $200-$50,000 and tiered rewards of Critical $30,000-$50,000, High $5,000-$15,000, Medium $1,000-$3,000, and Low $200-$700; it requires KYC for Medium+ reports and submission through HackenProof.

Assessment date: September 6, 2026. On-chain verification is unavailable in this run; therefore contract-level balances, venue allocations, collateral ratios, and exposure percentages are Not verifiable as of September 6, 2026. Primary dependencies and failure modes

• CEXs, derivatives venues, and trading counterparties — high risk. The strategy is described as basis trading/hedging, which requires spot and perpetual/futures execution. Solv disclosed an integration with Copper ClearLoop, an off-exchange settlement model intended to reduce assets held directly on exchanges. However, the specific CEXs, market makers, margin terms, legal counterparties, concentration limits, and recovery procedures are not disclosed in the reviewed evidence. Prior references to Binance, OKX, or Bybit remain unverified for this product.
• Custodian/settlement — material dependency. Copper is an identified infrastructure/custody dependency from Solv’s public announcement; ClearLoop reduces exchange custody exposure but does not eliminate Copper, settlement-bank, liquidation, or operational failure risk.
• Oracles and price manipulation — material. Solv documents use of Chainlink and RedStone for SolvBTC/LST pricing, including pushed RedStone data subject to heartbeat and deviation conditions. Risks include stale prices, relayer failure, feed deviation, thin-market manipulation, and incorrect BTC/wrapped-BTC conversion rates.
• Bridges/multichain — material. Solv documents Chainlink, LayerZero, Axelar, and native/free bridge routes across supported chains, including Ethereum, BNB Chain, Arbitrum, BOB, and Mantle. Bridge-message, mint/burn, validator, replay, and chain-halt failures could impair redemptions or create cross-chain insolvency.
• Underlying assets and external protocols. Public Solv material references Ethena basis-trading strategies and integrations involving Babylon, EigenLayer, Symbiotic, GMX, and Jupiter. These introduce separate smart-contract, funding-rate, slashing, liquidity, and issuer risks; actual allocation to Solv Basis Trading is Not verifiable as of September 6, 2026.
• Stablecoin/LST/RWA exposure. Analytics pages identify WBTC/cbBTC and a Mantle USDT pool, but these are stale third-party snapshots and not raw on-chain verification. RWA issuer/SPV exposure is Not verifiable as of September 6, 2026. Contradiction / data-quality callout: Third-party analytics report roughly 99%+ of tracked TVL on BSC in their stale snapshots, while the supplied chain list includes five chains. Exact current per-chain exposure is Not verifiable as of September 6, 2026. Stress scenarios: CEX insolvency or freeze; Copper/settlement failure; basis/funding-rate inversion; oracle manipulation or staleness; bridge exploit or chain halt; WBTC/cbBTC/USDT depeg; external protocol exploit or slashing; and simultaneous withdrawals causing liquidity mismatch. No evidence reviewed establishes an active dependency failure. Sources reviewed are not independent proof of solvency and should not be treated as assurance.

Solv Basis Trading appears to use a split custody model: user assets first sit in a custodial contract with multi-signature and time-lock controls, then governance authorizes movement into whitelisted strategy vaults rather than free-form external deployment. Solv also describes its BTC stack as using an event-driven custody pipeline with FROST threshold signing, which points to distributed institutional authorization rather than a single-key custodian. Withdrawal status is not verifiable as of 2026-09-06.

Segregated assets are not verifiable as of 2026-09-06. The available evidence indicates governed vault-based custody, but there is no independently verified source here confirming whether customer assets are legally or operationally segregated in the strict accounting sense.

On 3–6 March 2026 (reports differ between March 3 and March 5–6), Solv Protocol suffered a vault‑level exploit affecting a Bitcoin Reserve Offering (BRO) wrapper vault that underlies some Solv Basis Trading / SolvBTC strategies. The attacker abused a smart‑contract logic bug in the BitcoinReserveOffering contract, characterized as a double‑mint / self‑reentrancy‑like vulnerability in the mint flow via onERC721Received, allowing repeated minting of unbacked BRO tokens within a single transaction. This enabled inflation of roughly 135 BRO into about 567 million BRO, which were then swapped into approximately 38.0474 SolvBTC, corresponding to about $2.5–2.7m depending on the price reference.

The incident affected fewer than 10 users in that specific BRO vault; Solv stated that the core SolvBTC token contract and other vaults/strategies remained unaffected. Post‑incident, Solv paused the impacted vault, began an investigation with external security firms, and announced it would fully cover user losses while offering a 10% bounty to the attacker for return of funds. Public sources indicate a commitment to reimbursement but do not provide definitive, on‑chain‑verified confirmation of whether the stolen assets were actually recovered or if reimbursement has been completed to all affected users—this is Not verifiable as of 2026-09-03.

The exploit has been analyzed by multiple independent security firms with root cause identified as the double‑mint / callback flaw and recommendations for contract fixes; however, the exact status of redeployment or formal patching of the specific BRO vault contract is not exhaustively documented in independent sources and thus its remediation status is best classified as remediation_in_progress as of 2026‑09‑03.

Corrected scope: no confirmed direct exploit of the Solv Basis Trading product was identified. The relevant parent-protocol incident was an isolated, non-public Bitcoin Reserve Offering (BRO) vault on Ethereum, not a public Solv Basis Trading vault. On March 5, 2026, a smart-contract double-mint/reentrancy flaw involving an ERC-721 callback allowed 135 BRO to be inflated to approximately 567 million BRO across 22 iterations, then swapped for 38.0474 SolvBTC.

Realised loss was approximately $2.7 million. The affected scope was one BRO vault and two participants according to Solv’s post-incident review; contemporaneous reporting initially said fewer than 10 users. Solv contained the vault, investigated with external security firms, and stated that other vaults, public products, and user funds were unaffected.

Solv fully compensated affected participants by March 9, 2026. Remediation included mandatory external audits for every deployment, stricter internal risk assessment, approval, and change-management controls. Attacker proceeds were approximately $2.7 million in SolvBTC; recovery from the attacker itself is Not verifiable as of September 6, 2026.

Current status: resolved.

For Solv Basis Trading, the web results do not provide a verifiable, protocol-specific description of how key management is organized across Arbitrum, BSC, Bob, Ethereum, or Mantle. The only directly relevant statement is a third-party summary claiming Solv Protocol uses a non-custodial design and a multi-party controlled vault with MPC-style joint control by custodians, managers, and liquidators, but this is not independently confirmed and should be treated as an unverified marketing claim. So, the most accurate answer is: Not verifiable as of 2026-09-04 for the selected protocol and chains.

If you want a stronger institutional view, the next step would normally be to verify the exact contract addresses and role permissions on-chain and in explorers, but those checks are not available in this run.

Assessment as of September 6, 2026: High residual admin and verification risk; exact deployment-level controls are not verifiable. The official address registry identifies SolvBTC.TRADING on Ethereum at 0x325DC9EBceC31940C658aCACa45f8293418d811E and BNB Chain at 0x53E63a31fD1077f949204b94F431bCaB98F72BCE. It does not list a SolvBTC.TRADING address for Arbitrum, BOB, or Mantle. Therefore, addresses, explorer verification, proxy slots, implementation addresses, proxy-admin ownership, and role state for those deployments are Not verifiable as of September 6, 2026. Documented architecture (not independently on-chain verified): User → SolvBTC.TRADING vault receipt/token → Solv Vault / Fund Manager → Solv Guard + Safe/Vault Guardian → whitelisted DeFi venues, CEXs and off-chain strategies → NAV oracle → scheduled redemption.

Solv describes SolvBTC.TRADING as a multi-strategy product with DeFi, centralized-exchange and off-chain exposure; redemption is scheduled monthly on the 30th. This creates counterparty, custody, oracle, liquidity and operational-exit risk in addition to contract risk. Solv’s governance documentation states that upgrades use OpenZeppelin upgradeable contracts, with upgrade administration assigned to Gnosis Safe 0x0c2Bc4d2698820e12E6eBe863E7b9E2650CD5b7D; parameter administration is also described as Safe-controlled.

The documented model includes admin/minter/pool-burner roles and a Vault Guardian capable of restricting permitted targets and function selectors. Exact role holders for SolvBTC.TRADING, pause/withdrawal/fee/oracle/strategy permissions, renounced roles, Safe threshold, and whether the Safe can directly move vault assets are Not verifiable as of September 6, 2026. Timelock: documentation says a timelock “will be added,” while an independent governance record reported that upgrades were not yet timelocked. Current delay and deployment status are Not verifiable as of September 6, 2026; users should not assume an exit window. Worst case: compromised Safe/guardian/manager authority could upgrade logic, alter oracle or strategy routing, freeze redemptions, redirect assets, or impair NAV; CEX/off-chain losses may be unrecoverable.

Users cannot be confirmed to have an admin-independent exit because redemption is scheduled and strategy assets may be externally controlled. Contradiction callout: documented Safe/timelock protections are architecture claims; their current on-chain enforcement for this product is unverified.

Solv Protocol security review history shows 5 audits available, with the last audit delivered on 2024-06-27. Reported findings across the set were: 0 critical, 1 major (centralization), 1 medium (access control), 5 minor, and 1 informational issue. The issue status on the surfaced dashboard indicates the major finding was acknowledged, the medium finding was resolved, and the minor/informational findings were a mix of acknowledged and resolved.

The dashboard also states that only 51.21% of the codebase was audited, so the review was not a full-bytecode coverage match for all deployed code. For Solv Basis Trading specifically, the public review pages I found do not expose a separate auditor/date/scope breakdown, so a protocol-specific audit matrix is not verifiable as of 2026-08-29.

New report: Paladin Blockchain Security — LayerZero SolvBTC audit, published December 9, 2024. Scope: SolvBTC LayerZero/OFT adapter integration. Critical: 0; high: 0; medium: 0; low: 0; informational: 6. Fix status: recommendations reportedly addressed; itemized remediation is Not verifiable as of 2026-09-06. Covers deployed code: Not verifiable as of 2026-09-06.

New report: Quantstamp — xSolvBTC audit, published July 10, 2025. Scope: xSolvBTC contracts; exact files and commit are Not verifiable as of 2026-09-06. Critical/high/medium/low/informational findings: Not verifiable as of 2026-09-06. Fix status: Not verifiable as of 2026-09-06. Covers deployed code: Not verifiable as of 2026-09-06.

New report: OpenZeppelin — Solv Mainnet Minter audit, audit period November 25–26, 2024. Scope: Solv mainnet minter contract. Critical: 0; high: 0; medium: 0; low: 3; informational: 4. Fix status: all findings reportedly resolved. Covers deployed code: Not verifiable as of 2026-09-06.

New report: OpenZeppelin — SolvBTC Blacklist audit, audit period December 12–13, 2024. Scope: SolvBTC blacklist functionality. Critical: 0; high: 1; medium: 0; low: 2; informational: 13. Fix status: all findings reportedly resolved. Covers deployed code: Not verifiable as of 2026-09-06.

New report: Offside Labs — SolvBTC Vault audit, audit period September 12–20, 2025; report file is dated October 2025. Scope: SolvBTC Vault. Critical: 0; high: 0; medium: 2; low: 1; informational: 10. Fix status: findings reportedly fixed or acknowledged; per-finding status and deployed-code match are Not verifiable as of 2026-09-06.

New report: Salus — SOLV token Ethereum audit, published May 6, 2026. Scope: SOLV token Ethereum deployment. Critical: 0; high: 0; medium: 0; low: 1; informational: 2. Fix status: Not verifiable as of 2026-09-06. Covers deployed code: Not verifiable as of 2026-09-06. This is token-level context, not a basis-trading-module-specific audit.

Secondary source summarizing Solv Protocol’s overall audit coverage; useful for institutional context but not an on-chain‑verified or basis‑module‑specific audit.

Quantstamp — Solv Protocol SolvBTC audit; audit period July 9–17, 2024. Scope: SolvBTC, SolvBTCYieldTokenOracleForSFT, SolvBTCMultiAssetPool, SftWrapRouter, and SftWrappedTokenFactory; OpenFundMarket and SolvWrappedToken were explicitly out of scope. Critical: 0.

High: 0. Medium: 1 — attacker can drain value from a multi-asset pool. Low: 4 — including stale NAV risk and SFT-slot issues.

Findings status: 3 fixed, 3 acknowledged, 1 mitigated. Covers deployed code: Not verifiable as of 2026-09-05.

A Quantstamp report surfaced for Solv BTC Redemption. The snippet says the audit found no major vulnerabilities or critical security issues, and the findings were primarily low-severity or design-level considerations: lack of user slippage protection, global withdrawal limit griefing potential, and strong dependency on correct admin configuration. However, the surfaced snippet does not provide a complete findings table, and the exact overlap with Solv Basis Trading deployed code is not verifiable as of 2026-08-29.

Audit of Solv Protocol BTC redemption contract (BTCPlusRedeem), part of Solv’s BTC products that underpin basis trading strategies.

Salus — Solv Protocol V3 Audit Report v2; publication/audit date: March 10, 2023. Scope: Solv Protocol V3 abilities and common contracts in solv-contracts-v3. Critical: 0.

High: 1 — users could subscribe for free when price × value < 10**decimals. Medium: 1 — centralization risk. Low: 3 — missing upgradeable storage gap, uninitialized upgradeable dependency, and silent doApprove() failure for an EOA.

Findings status: high and low findings resolved; medium centralization risk acknowledged. Covers deployed code: Not verifiable as of 2026-09-05.

Salus — Solv Protocol Open-Fund Audit Report; publication date: July 31, 2023. Scope: OpenFundMarket, FCFSMultiRepayableDelegate/Concrete, OpenFundShare/Redemption components, and related helpers. Critical: 0.

High: 2 — repayment-based fund-pool DoS; incorrect slot handling in setRedeemNav(). Medium: 3 — fundraising-time access control; claimableValue() miscalculation; users unable to claim all value. Low: 2 — subscribe() precision loss; invalid time check.

Findings status: all resolved except incorrect storage-gap size, acknowledged. Covers deployed code: Not verifiable as of 2026-09-05; audited commit differs from any unverified deployed bytecode.

Salus — SolvBTC audit report; publication date: November 28, 2024. Scope: SolvBTCRouterV2. Critical: 0.

High: 0. Medium: 0. Low: 1 — unexpected event emission when removing a nonexistent KYC SBT verifier.

Informational: 1. Finding status: low issue resolved in commit 995148c; informational status is not fully extractable from the available report text. Covers deployed code: Not verifiable as of 2026-09-05.

Protocol‑level audit of Solv Protocol V3 contracts on EVM chains; likely foundational for several Solv products, but direct linkage to the solv-basis-trading deployment set is not confirmed.

Security audit of Solv 2.0 DeFi contracts; covers broader Solv architecture and authority model rather than a named “basis trading” module.

Solv Basis Trading is a yield product stack built on Solv Protocol, so founder/team reality is that of Solv Protocol itself rather than a separate anonymous team. ### Founders & Core Team

• Founders (public, non‑anon):
• Ryan Chow (Ryan C.) – Founder/CEO of Solv Protocol.
• Meng Yan (Yan Meng) – Co‑CEO/co‑founder, co‑author of the ERC‑3525 token standard.
• Will Wang – Co‑founder, CTO, chief architect; also associated with ERC‑3525 authorship.
• Some sources add Mike Meng as a founder. All four have named LinkedIn profiles and visible public histories in tech/finance, indicating a fully doxxed team, not pseudonymous. ### Prior Projects, Track Record, Hacks
• Ryan Chow: prior work includes Beijing Youzan Technology and a financial analyst role at Singularity Financial, with focus on blockchain and regulation.
• Will Wang: ~18–20 years in financial IT, led large‑scale banking system development, recipient of a Zhongguancun outstanding contribution award.
• Meng Yan: former VP at CSDN and a recognized crypto/KOL figure.
• No credible records of major protocol hacks or insolvency events tied to Solv Protocol or Solv Basis Trading found in independent coverage as of 2026‑09‑04. Not verifiable as of 2026‑09‑04 for minor/security‑incident history beyond public reports. ### Public vs. Anon, Office, Jurisdiction
• Multiple profiles list Singapore as the operating location for founders and Solv Protocol roles, with additional presence in Hong Kong/Canada at individual level.
• Crunchbase tags headquarters in Asia‑Pacific/ASEAN/Southeast Asia, consistent with Singapore as primary base.
• Existence of a physical office address, legal entity details, and precise onshore/offshore structuring are Not verifiable as of 2026‑09‑04 from independent sources. ### Real Business vs. Web Front
• Solv Protocol shows:
• Venture‑backed funding and named investors (e.g., Binance Labs, Blockchain Capital, Nomura).
• Large user base and TVL for BTC yield products and SolvBTC, per independent analytics and exchange/education content.
• Detailed descriptions of BTC basis trading, funding‑rate arbitrage and RWA yield strategies in third‑party breakdowns, not just its own marketing. Overall, the founder transparency and professional background are strong, and independent data points to an active, revenue‑generating BTC yield business, though full corporate/legal structuring remains partially unverified.

Solv Basis Trading is a structured-yield product line within the broader Solv Protocol ecosystem, not a standalone protocol entity. Reputation assessment therefore focuses on Solv Protocol and its basis‑trading vaults. Identity & background

• Solv Protocol is a DeFi project focused on “yield vaults” and “voucherized assets,” launched originally on Ethereum and later expanded to Arbitrum, BNB Chain, Mantle, and others.
• The protocol is backed by recognizable crypto investors including Binance Labs, Spartan Group, and others.
• Founding team is publicly associated with Solv but remains relatively low‑profile versus blue‑chip DeFi teams; detailed bios are limited. Audits & security track record
• Solv states that multiple components of the protocol (including yield vaults) have been audited by firms such as SlowMist and BlockSec; these reports are referenced in documentation and announcements, but are not always easily accessible via independent auditor sites for each specific vault.
• No widely reported critical hacks, insolvencies, or protocol‑level rug pulls involving Solv Basis Trading were found in recent DeFi news or incident trackers as of 2026‑09‑04. Sentiment & criticisms
• General sentiment toward Solv in media and analytics platforms is moderately positive to neutral, focusing on innovation in structured products and partnerships with exchanges and ecosystems (e.g., BNB Chain, Arbitrum).
• Main implicit risk criticisms relate to:
• Complexity of basis‑trading and structured‑yield strategies, which may be difficult for retail investors to fully understand.
• Counterparty and venue risk where strategies depend on centralized exchanges or specific perp venues; this is mentioned generically in structured‑product discussions rather than as a direct allegation against Solv. Legal/regulatory & sanctions
• No evidence of regulatory enforcement actions, sanctions lists, or court cases specifically naming Solv Basis Trading or Solv Protocol was found in major regulatory databases or mainstream crypto legal coverage as of 2026‑09‑04. Fraud/rug/insolvency allegations
• No credible reports of fraud, rug pulls, or project‑level insolvency tied to Solv Basis Trading were identified in independent media, incident trackers, or major social‑media discussions as of 2026‑09‑04. Unresolved concerns
• Strategy details, risk models, and independent performance verification for basis‑trading vaults are relatively thin in public, non‑Solv sources; much information comes from Solv’s own documentation, which is therefore “unverified marketing claim” by this framework.
• On‑chain TVL, per‑chain exposure (Arbitrum, BSC, Bob, Ethereum, Mantle), and real PnL for Solv Basis Trading are Not verifiable as of 2026‑09‑04 under this run’s constraints (no Dune MCP / no direct on‑chain queries).

Economic model (as of September 6, 2026)

• Strategy: Solv Basis Trading is described as using basis trades and hedging to target low-risk, market-neutral returns for Bitcoin holders. This establishes market-neutral intent, not proof that every position is delta-neutral.
• Assets in/out: Aggregator-tracked pools list BTCB (BSC), WBTC (Ethereum, BOB, Arbitrum), cbBTC (Ethereum), and USDT (Mantle). These are aggregator labels, not on-chain-verified holdings.
• Yield source: Basis/funding or spread capture is the stated core mechanism. APY Hub additionally describes trading fees, borrower interest, and token incentives as possible DeFi yield sources; therefore returns may be partly subsidized, but the organic share is not disclosed.
• Organic vs subsidized: organic_yield_pct: null. Incentive dependence is plausible from the published “base APY vs reward APY” framing, but no product-level split is verifiable.
• Leverage/looping/restaking/external exposure: leverage_ratio: null. Actual leverage, loops, restaking, exchange/custodian, derivatives, and counterparty exposures are Not verifiable as of September 6, 2026. Basis trading inherently may require short/derivatives venues, but this cannot be assumed.
• Lock-ups/withdrawals: Product-specific terms, gates, and limits are Not verifiable as of September 6, 2026. Solv’s separate BTC+ documentation describes scheduled redemptions and BNB-only instant redemption, but this should not be extrapolated to Basis Trading.
• Fees/revenue/collateral: Product fees, protocol revenue capture, collateral ratios, liquidation rules, and performance-fee allocation are Not verifiable as of September 6, 2026. TVL and trend contradiction > Aggregator conflict: DeFiLlama reports $199.5m TVL: BSC $199.48m (~99.99%), Arbitrum $23.4k, Ethereum $3.15k, Mantle $23.62; BOB is not shown. It reports 6 pools and 0% average APY, with +25.9% 30-day TVL growth. > > APY Hub reports $461.41m, including BSC $233.44m, Ethereum $182.94m, BOB $42.21m, Arbitrum $1.85m, and Mantle $0.96m—but also displays 0% APY. This is a material unresolved data contradiction; DeFiLlama is the selected TVL reference, while APY history/volatility/sustainability are Not verifiable as of September 6, 2026. Dune was unavailable in this run; no on-chain claims are asserted.

As of September 6, 2026, reserves/treasury for the specifically identified Solv Basis Trading product are not verifiable as of 2026-09-06.

• Liquid reserve size: Not verifiable as of 2026-09-06. DeFiLlama reports product TVL as an analytics estimate, not a treasury or reserve attestation, and does not establish immediately liquid assets, ownership, or custody.
• Reserve addresses / on-chain balances: Not verifiable as of 2026-09-06. Dune on-chain verification was unavailable in this run; no independently confirmed reserve-address registry or chain-by-chain balance schedule was found.
• Composition: Not verifiable as of 2026-09-06 for Solv Basis Trading. Solv’s documentation describes BTC reserve categories for SolvBTC—native BTC, BTCB, WBTC, FBTC, cbBTC, BTC.b, and tBTC—but this does not prove that those assets constitute reserves of the Basis Trading product.
• Custody and control: Solv documentation claims that BTC reserves are managed through the FROST threshold-signing network and distributed signing authority. This is an unverified marketing claim for purposes of Basis Trading treasury analysis; no product-specific custody agreement, custodian account, signer set, or control evidence was located.
• Reserve policy: A reserve policy is documented for SolvBTC, including reserve classes, minting caps, and cross-chain rate limits, but no separate Basis Trading reserve policy or segregation framework was verified.
• Attestations: Not verifiable as of 2026-09-06. No independent, product-specific reserve attestation, proof-of-liabilities report, auditor-issued balance confirmation, or continuously queryable reserve report was found. Contradiction / scope note: The retrieved SolvBTC reserve materials should not be treated as evidence of Solv Basis Trading reserves. The available analytics TVL figure is not equivalent to liquid reserves, and no liability figure can be derived from it.

Scope: Solv Basis Trading is a Solv Protocol product (SolvBTC.TRADING), not a separately tokenized protocol. No distinct Basis Trading native token was identified; the parent token is SOLV. • Token/address: SOLV (Solv Protocol). BNB Chain: 0xabE8E5CabE24Cb36df9540088fD7cE1175b9bc52.

Ethereum: 0x169E36F327cAA83d004f5c2668AC25A1424C940d. Officially documented SOLV addresses for Arbitrum, BOB and Mantle: Not verifiable as of September 4, 2026. SolvBTC.TRADING itself is not SOLV: Ethereum 0x325DC9EBceC31940C658aCACa45f8293418d811E; BNB 0x53E63a31fD1077f949204b94F431bCaB98F72BCE.

• Supply/valuation: genesis supply 8.4B; stated maximum supply 9.66B, dynamically increasable through governance for Bitcoin Reserve Offerings. CoinGecko reports 5.525B circulating, ~$16.63M market cap and ~$29.07M FDV as of September 4, 2026. These are aggregator figures, not on-chain verified.

• Utility/governance: SOLV is intended for DAO voting, staking/emissions through Solv’s Staking Abstraction Layer, and fee discounts. vSOLV was a time-locked rewards/buyback mechanism; 2.5% of supply was allocated, with 1:1 redemption terms at program maturity. No confirmed protocol revenue-share entitlement was found. • Emissions/unlocks: published allocation is: private investors 28.86%, team/advisors 13%, community rewards/DAO treasury 18%, external-partner rewards 8.5%, Binance Megadrop 7%, community airdrop 8.5%, ecosystem 8.14%, business development 4%, vesting-voucher holders 1%, liquidity 3%; BRO reserve 13.04% of maximum supply.

Third-party trackers report a January 16, 2025–December 17, 2028 vesting window and a September 17, 2026 unlock of ~189.68M SOLV. Whether announced unlocks actually occurred on-chain: Not verifiable as of September 4, 2026. • Controls/concentration/liquidity: SOLV top-holder concentration, insider-wallet attribution, native-token mint/blacklist/fee-switch permissions, and DEX liquidity depth: Not verifiable as of September 4, 2026.

Main reported listings are Binance, LBank, Bitvavo, Bitunix, Bybit and others; CoinGecko’s displayed liquidity table is primarily CEX data, not reliable DEX-depth evidence.

For Solv Basis Trading, a Bitcoin drop below $10,000 would be a severe stress event, but the protocol’s actual loss mechanism is not verifiable as of 2026-09-04 from the available sources. DefiLlama only identifies the protocol as a basis-trading product and provides TVL/statistics, but the search results do not include chain-level position data, leverage, liquidation thresholds, or custodial structure needed to quantify impact. What can be said with higher confidence is the market-path risk: basis trades combine spot exposure with short futures exposure, and in stress conditions they can face basis widening, funding withdrawal, margin calls, and counterparty risk.

If BTC fell below $10,000, those risks would likely intensify across any basis-trading strategy, especially if the move were accompanied by forced deleveraging, liquidity contraction, or exchange/counterparty stress. Because Dune/on-chain verification is unavailable in this run, the following are not verifiable as of 2026-09-04: the protocol’s exact exposure to BTC price, per-chain TVL split across Arbitrum, BSC, Bob, Ethereum, and Mantle, open liquidation bands, and whether any user funds are held in vaults, hedged externally, or rehypothecated. I cannot confirm whether a $10k BTC move would cause immediate liquidation, delayed NAV impairment, or no direct effect on user principal without those inputs. Stress-analyst view: the key question is not just BTC price, but whether the protocol’s hedges remain executable and its counterparties remain solvent.

In a BTC sub-$10k scenario, the most likely transmission channels are basis dislocation, margin depletion, liquidity freeze, and counterparty default rather than spot-price loss alone.

Not verifiable as of 2026-09-04. The only protocol-specific exposure figure available here is DeFiLlama TVL for Solv Basis Trading at $147.73m, with $147.49m on BSC; the other requested chains (Arbitrum, Bob, Ethereum, Mantle) are not broken out in the provided results, so I cannot verify the full multi-chain collateral mix needed for a 20% largest-collateral depeg stress. If the largest collateral asset depegs by 20%, the portfolio impact would equal 20% of that asset’s *exposed* value, but the actual loss, insolvency risk, or liquidation shortfall cannot be calculated from the available data because the collateral composition, leverage, haircuts, and liabilities are not verifiable here.

Not verifiable as of 2026-09-04. The only direct chain exposure observable in the results is BSC, which accounts for essentially all reported TVL in the snippet, but that does not prove it is the largest collateral asset or that all TVL is collateral at risk.

For Solv Basis Trading, the only verifiable counterparty-insolvency path I could confirm from the available web sources is the protocol’s stated design intent around isolating centralized-exchange exposure in a protection layer and using diversified venues and collateral outside exchanges to reduce venue-default risk. For this run, on-chain verification is not available, so any chain-by-chain contract-level loss waterfall is Not verifiable as of 2026-09-04. Expected loss path: if the top counterparty on the basis-trading leg becomes insolvent, the first loss is the shortfall between the venue’s owed value and what can actually be recovered from that venue’s collateral or position unwind. If recovery is incomplete, the residual gap would flow to the protocol’s protection layer / reserve layer rather than directly to the core user-facing stablecoin layer, per the documented architecture intent. Who absorbs it: the documentation says the protection layer (RLP) is intended to absorb centralized-exposure losses, while user-facing assets are meant to be insulated from exchange default.

A separate source describing Solv’s smart-contract repository confirms the protocol has dedicated core contracts for issuing and trading its products, but it does not provide a verifiable insolvency waterfall. Compensation: the available material indicates compensation would come from the protocol’s protection reserve rather than from the insolvent counterparty itself, but the exact redemption rate, haircuts, or timing are Not verifiable as of 2026-09-04. Impact path through smart contracts: the verified path is only at a high level: exposure is managed in protocol contracts, losses are meant to be isolated in the protection layer, and any residual impairment would then affect that layer before reaching user claims. The precise contract-by-contract propagation across Arbitrum, BSC, Bob, Ethereum, and Mantle is Not verifiable as of 2026-09-04. Chain split / exposure share: Not verifiable as of 2026-09-04 for each chain and therefore no reliable % split can be stated.

For Solv Basis Trading, a stress scenario of committed fraud by the DAO or owners is Not verifiable as of 2026-09-04 from the available sources. The search results do not provide protocol-specific evidence that Solv Basis Trading’s DAO, owners, or controllers committed fraud, nor do they identify the protocol’s verified governance structure, controlling parties, or incident history. What *is* supported is only the broader legal and risk context: regulators have treated some DAO-related conduct as actionable, including the SEC’s DAO report and the CFTC’s action against Ooki DAO, and academic/legal sources describe cases where DAO governance or private-key control created liability or theft risk.

Those sources do not establish fraud by Solv Basis Trading itself. For this protocol and this stress case, the prudent risk assumption is:

• Potential loss mechanism: insiders or governance controllers could misuse admin, upgrade, treasury, or key-management powers to divert user funds or alter protocol rules.
• Impact scope: all deployed chains listed for the protocol could be affected if a shared admin key or cross-chain governance control exists.
• Confidence: low, because the necessary protocol-specific evidence is missing. No protocol-specific fraud event, governance admission, court finding, or verified on-chain incident was identified in the provided material, so the correct status remains Not verifiable as of 2026-09-04.

Stress finding: the protocol’s primary yield source can go negative over a 30-day window if basis/funding economics flip and/or hedged carry is insufficient to cover costs. For Solv-style basis trading, this is a plausible stress outcome because the yield is driven by spread capture and funding economics, and basis trades can deteriorate when funding conditions tighten or funding turns adverse. What the available sources support:

• Basis-trade returns are sensitive to funding-market stress; tighter funding, higher repo costs, and margin pressure can force deleveraging and compress or reverse the trade’s profitability.
• In Solv-related yield disclosures, the protocol states that overall yield is not guaranteed to stay positive and that negative overall yield is possible in principle.
• Independent DeFi references on similar short-perp/funding structures note that when funding turns negative, the protocol may have to pay rather than receive carry, which can make yield negative if the adverse regime persists. For a 30-day stress scenario, the key risk statement is: if the basis spread narrows materially or turns negative while financing, hedging, or rebalancing costs remain elevated, the primary yield source can be negative for the month. Not verifiable as of 2026-09-04: chain-by-chain exposure, live 30d realized yield, and whether Solv Basis Trading’s current implementation has any reserve, smoothing, or floor mechanism that would prevent a negative monthly yield.

As of September 13, 2026, governance appears operationally controlled by Solv-administered Safe/Governor infrastructure, not demonstrably by SOLV token holders. Solv documentation assigns upgrade administration and business-parameter control to a Gnosis Safe at 0x0c2Bc4d2698820e12E6eBe863E7b9E2650CD5b7D; privileged roles include admin assignment of minter/burner permissions and pool-level burning. Solv Guard adds vault-specific authorization over permitted contracts/functions, investment/redemption authority, destinations, whitelisted assets, native-token transfers, and governance-rights termination.

Whether these controls apply identically to Solv Basis Trading vaults on Arbitrum, BSC, Bob, Ethereum, and Mantle is Not verifiable as of September 13, 2026. DAO/process. Solv claims SOLV holders can submit and vote on proposals through BNB Chain governance, but the documentation says further details are forthcoming. DeFiLlama records only four historical proposals, all from 2022–2023, and zero proposals in the last 30 days; this supports a conclusion that DAO governance is currently limited or symbolic rather than proven control of upgrades and parameters. Voting concentration and top holders via Dune: Not verifiable as of September 13, 2026 (Dune unavailable). Timelock/multisig. The smart-contract governance page says a timelock “will be added,” while Solv Guard describes a timelock concept without specifying delay.

Exact deployment, delay, Safe threshold, signer identities, signer independence, and emergency-bypass configuration are Not verifiable as of September 13, 2026. The cited Safe address is documented, but current on-chain ownership cannot be confirmed without Dune/RPC verification. Company/frontend. Terms identify Solv Legos Ltd. as the interface provider. Solv’s legal footer identifies Solv Protocol Limited as Gibraltar-incorporated, but gives contradictory company numbers 111928 and 118088; directors were not identified. Contradiction: Solv markets community governance, but disclosed privileged Safe/Guardian powers remain the effective control surface; the DAO’s ability to control upgrades is unproven. Structured fields: timelock=null; timelock_delay_hours=null; multisig_threshold=null; multisig_owners=null; admin_can_drain=null; emergency_bypass=null; dao_governance=false.

Legal & regulatory assessment — as of September 4, 2026 Entity / jurisdiction. The Terms of Use identify Solv Legos Ltd. as the interface provider, but do not state its incorporation jurisdiction in the document. Independent corporate-profile data identifies Solv Legos Ltd. with the British Virgin Islands. A separate Solv publication identifies Solv Protocol Limited as incorporated in Gibraltar and regulated by the Gibraltar FSC as a DLT institution/credit institution.

This indicates a potentially multi-entity structure; which entity legally operates Solv Basis Trading is Not verifiable as of September 4, 2026. The Terms choose Singapore law and SIAC arbitration. ToS / restrictions. The Terms prohibit U.S. users, Canada, Singapore, China, Russia, sanctioned persons, comprehensive-embargo jurisdictions, illegal activity, market manipulation, and VPN circumvention.

They describe services as experimental, disclaim fiduciary duties and most liability, and waive court/jury/class-action routes in favor of arbitration. KYC/AML / data protection. KYC may be mandatory; Solv reserves on-chain/off-chain AML screening, beneficial-owner checks, source-of-funds verification, transaction monitoring, and collection of identity/biometric data through third parties. Its privacy policy permits affiliate/service-provider sharing, regulator or law-enforcement disclosure, international transfers, and retention for legal/security purposes.

Specific GDPR, BVI, Gibraltar, or Singapore compliance status is Not verifiable as of September 4, 2026. Classification / warnings. Solv self-describes its virtual assets and yield products as not securities, says it is not federally/state regulated or SEC-registered, and excludes U.S. persons. This is an unverified marketing/legal-position claim, not a regulator determination.

The products’ yield, tokenization, custody, and structured-finance features could create jurisdiction-specific securities, collective-investment, derivatives, custody, or VASP exposure based on substance. Enforcement / sanctions / cases. No regulator enforcement action, court case, or sanctions designation against Solv Basis Trading or an identified operating entity was located in the reviewed sources: Not verifiable as of September 4, 2026. This is not a clearance. CONTRADICTION / actual risk: formal disclaimers emphasize decentralization and no custody, while the legal documents contemplate KYC, AML monitoring, yield-product management, affiliates, and third-party custodians. Legal-form separation therefore does not eliminate substance-over-form regulatory or counterparty risk.

Legal entity per GLEIF: Solv Legos Ltd (LEI 984500115C6D806C9C17; jurisdiction VG; registration ACTIVE). OFAC SDN screening of 'Solv Legos Ltd', 'Solv Basis Trading': no match. SEC litigation and administrative release feeds: no mention.

Solv Basis Trading does not appear to issue its own stablecoin, so own_stablecoin is false. The stablecoin exposure identified in the gathered sources is USDT on Mantle, but no verifiable depeg event, count, last depeg date, or maximum depeg percentage could be confirmed from the available web evidence. Not verifiable as of 2026-09-06.

Solv Basis Trading combines BTC custody, token issuance, cross-chain distribution, and market-neutral trading across DeFi, centralized exchanges, and off-chain venues. The principal risks are therefore structural rather than purely directional. Chain-by-chain TVL, exposure, reserve coverage, and current vault positions are Not verifiable as of September 5, 2026 because on-chain verification was unavailable; residual risk remains materially uncertain.

Solv Basis Trading’s top strengths are: (1) low-volatility yield design—it uses basis trades, hedging, and market-neutral positioning to target relatively steady returns rather than directional beta; (2) BTC-native strategy fit—the product is explicitly designed for Bitcoin holders seeking yield without giving up BTC exposure; (3) multi-strategy diversification—Solv’s broader BTC yield stack combines basis trading with other yield sources, which can reduce dependence on any single market regime; (4) institutional framing and risk controls—Solv emphasizes verifiable reserves, on-chain auditability, and structured risk management; and (5) cross-chain distribution and composability—the Solv ecosystem is built for multi-chain access and broad BTCFi integration. Because this run cannot use on-chain verification, chain-by-chain TVL and exposure splits are Not verifiable as of 2026-09-04.