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