protocol identification
two sourcesMEV Capital is a DeFi / on-chain liquidity and risk-management protocol and investment manager focused on market-neutral yield strategies. Its public website is mevcapital.com, and its documentation appears under a GitBook vaults protocol page; the site and docs describe activity since 2020–2021, but a precise launch date is not verifiable as of 2026-08-29. Chain coverage is multi-chain. A third-party tracker reports deployments on Ethereum, Hyperliquid L1, Sui, Base, Avalanche, Arbitrum, Unichain, and Sonic, with additional chains beyond the subset in your prompt; however, because on-chain verification is unavailable in this run, the exact chain-by-chain TVL/exposure split is not verifiable as of 2026-08-29. Native token status is not clearly established from the independent sources reviewed; no authoritative source in this pass confirms a canonical MEV Capital native token, so this is not verifiable as of 2026-08-29. Contract addresses: the accessible sources surfaced token pages for MEV Capital-branded assets and a GitBook promising live contract links, but I could not cross-check any main production contract addresses against a second independent source, nor against chain explorers, in this no-tools run. Therefore the main contract addresses and explorer verification status are not verifiable as of 2026-08-29. Fork lineage: the available evidence points to MEV Capital as a risk-curation / vault-management firm rather than an obvious code fork of a single upstream protocol. I did not find independent evidence in this pass that it is a direct fork, what exact upstream it changed, or that any fork-specific modifications were audited. Malicious-modification history in similar forks is likewise not verifiable as of 2026-08-29. The strongest independently sourced finding is that MEV Capital presents itself as an EU-based DeFi investment and risk-management firm active since 2020/2021, with a GitBook vaults documentation set and a broad multi-chain footprint; everything else above requires on-chain or explorer verification that is unavailable in this run.