alpha signal: CRV dev health on curve

curvefi/curve-contract flagged dev-health: zero activity 30d. repo not archived but commits, contributors, merged PRs all zero. baseline score was already 0.0 so no regression to measure. 53 open issues, 1101 stars. zero activity on a core contract repo for a protocol that proce

curvefi/curve-contract flagged dev-health: zero activity 30d. repo not archived but commits, contributors, merged PRs all zero. baseline score was already 0.0 so no regression to measure. 53 open issues, 1101 stars.

zero activity on a core contract repo for a protocol that processes billions in volume. this is either a sign the code is considered finished or the dev team has moved to other repos. curve’s governance is active elsewhere (dao, fee adjustments, cross-chain deployments). the contract layer being quiet doesn’t necessarily mean the protocol is dead.

dev silence on a core contract repo usually precedes one of three things: a governance shift where the team is working on new versions under a different repo, a pivot to a new architecture, or gradual ossification where the protocol runs on autopilot. curve’s liquidity and volume suggest the latter is more likely.

what’s the last time you checked which repo your defi protocol actually develops on?


Originally published on FalsifyLab Substack.


Write a comment
No comments yet.