Bitcoin SV

Track record score 76 out of 100. Bitcoin SV has been live for 8.4 years, with regulatory cleanliness scoring 100 (0 regulatory actions). There is 1 historical incident recorded with an incident cleanliness of 80, and research also raised 2 additional concern(s) based on agent red flags (score 30). Overall, the long operational history and clean regulatory record help offset isolated past issues.

Developer health score 14 out of 100. Public development signals are weak: 0 commits in the last 4 weeks and 0 PR contributors, alongside relatively modest activity metrics (27 GitHub stars and 299 forks). The “norecentcommits” flag aligns with the low score, suggesting the repository has not shown current momentum or active contributions recently.

Network security score 67 out of 100. The chain shows strong maturity (chain age 8.4 years, score 93) and a defined supply cap (hard cap 21,000,000, score 100), with circulating ratio at 100 (100% of total supply circulating). Economic security is lower (score 32) with market cap of $328,708,895, and there is 1 historical incident on record (incident history score 75), keeping the bucket in the mid-range rather than top tier.

Social & behavioral score 51 out of 100. Sentiment is mixed but somewhat positive (75% up / 25% down), while social audience metrics are limited (TW linked; audience score 25). Agent risk signals indicate 0 allegations, but there is 1 bad press and 1 incident noted (score 85 for risk signals), and research also raised 2 additional concern(s) (agent red flags score 30). A “hackorexploit_history” flag is present in this bucket.

Adoption & liquidity score 39 out of 100. Liquidity and trading depth are moderate, with 24h volume of $9,312,367 (score 24) and a smaller market-cap tier signal (score 0) for market cap $328,708,895. Exchange listing data is broader at 32 CEX listings (83 overall, including 14 green-trust), but the lower volume level limits the overall liquidity score.

Even with a 49.4/100 safety score (CCC), inherent crypto risk remains for this L1 protocol: developer momentum appears inactive recently, economic security is not strong, and there are flags tied to hack or exploit history plus incident records. As with all public blockchains, risks can include technical events, market liquidity changes, and reputational effects that impact holders and builders over time.