BlackHartPublic score as of Nov 7, 7 days behind. Live subscribers see every move the moment it lands.
Go live for $29
Lido
Score history
Model updateEvery Score Move
Live for subscribersOpen any move to see what changedMay 20down 2Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 19up 2Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 19up 4Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 17down 1Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 15down 17Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 6down 18Model updateMethodology update
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
Dimensions
12 dimensions, 10 apply to Lido. Open one to see how it is scored.Access controlscore 88weight 18%
Admin keys, roles, permissions and the checks that guard them.
Economic soundnessscore 85weight 13%
How the economic design holds up under flash loans, MEV, liquidation cascades and bad incentives.
Oracle integrityscore 92weight 13%
How prices reach the protocol, and how hard they are to manipulate or let go stale.
Maturityscore 93weight 12%
Time in production, value secured over time, audits, bounties and incident history.
- Live since
- Dec 17, 2020 (70 months)
- TVL
- $15B+
- Audits
- Oxorio, Jun 2023
- Certora (Formal Verification), Apr 2023
- Statemind, Apr 2023
- MixBytes, Aug 2022
- Bug bounty
- Immunefi, up to $2,000,000
Governancescore 88weight 10%
Admin key concentration, timelocks and how upgrades happen.
Adversarial resiliencescore 47weight 10%
How the code holds up under independent adversarial research.
Operational securityscore 66weight 10%
Incident response, deployment hygiene, key management and monitoring.
- GitHub scan
- lidofinance/lido-dao on May 20
- Branch protection
- No
- Required reviews
- 0
- Signing ratio
- 100%
- Commits in 90 days
- 50
- PR review ratio
- 43%
- Has CI
- Yes
- CI success rate
- 40%
- Security policy
- Yes
- Deployment hygiene
- 73 of 100
- Development practices
- 44 of 100
- Emergency history
- 75 of 100
- Incident response
- 65 of 100
- Key management
- 70 of 100
- Monitoring
- 85 of 100
Compositional riskscore 80weight 5%
External dependencies and the surface where contracts and integrations interact.
Cascade exposurescore 48weight 5%
Failures upstream that could spread into the protocol, and the damage if it fails.
Supply chainscore 88weight 4%
Compiler versions, libraries, build reproducibility and proxy patterns.
- Dependabot
- No