BlackHartPublic score as of Nov 7, 7 days behind. Live subscribers see every move the moment it lands.
Go live for $29
Stargate V2
Score history
Model updateEvery Score Move
Live for subscribersOpen any move to see what changedMay 15down 11Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 13down 56Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 6up 18Model updateMethodology update
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
Dimensions
12 dimensions, 11 apply to Stargate V2. Open one to see how it is scored.Access controlscore 80weight 16%
Admin keys, roles, permissions and the checks that guard them.
Economic soundnessscore 82weight 12%
How the economic design holds up under flash loans, MEV, liquidation cascades and bad incentives.
Oracle integrityscore 88weight 12%
How prices reach the protocol, and how hard they are to manipulate or let go stale.
Maturityscore 78weight 11%
Time in production, value secured over time, audits, bounties and incident history.
- Live since
- Apr 1, 2024 (31 months)
- TVL
- $500M+
- Audits
- Zellic, Mar 2024
- Quantstamp, Jun 2022
- Bug bounty
- Immunefi, up to $10,000,000
Adversarial resiliencescore 50weight 10%
How the code holds up under independent adversarial research.
Compositional riskscore 72weight 9%
External dependencies and the surface where contracts and integrations interact.
Governancescore 75weight 9%
Admin key concentration, timelocks and how upgrades happen.
Cross-chain messagingscore 68weight 9%
Bridge trust model, sequencer risk, fraud proofs and replay risk.
Operational securityscore 61weight 9%
Incident response, deployment hygiene, key management and monitoring.
- GitHub scan
- stargate-protocol/stargate-v2 on May 20
- Branch protection
- No
- Required reviews
- 0
- Signing ratio
- 100%
- Commits in 90 days
- 30
- PR review ratio
- 90%
- Has CI
- Yes
- CI success rate
- 40%
- Security policy
- No
- Deployment hygiene
- 73 of 100
- Development practices
- 41 of 100
- Emergency history
- 75 of 100
- Incident response
- 65 of 100
- Key management
- 70 of 100
- Monitoring
- 40 of 100
Cascade exposurescore 100weight 5%
Failures upstream that could spread into the protocol, and the damage if it fails.
Supply chainscore 80weight 4%
Compiler versions, libraries, build reproducibility and proxy patterns.
- Dependabot
- No