BlackHartPublic score as of Nov 7, 7 days behind. Live subscribers see every move the moment it lands.
Go live for $29
Aztec
Score history
Model updateExploitEvery Score Move
Live for subscribersOpen any move to see what changedMay 16up 1Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 16down 1Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
May 15up 2Model updateDimensions rescored
BlackHart's method or evidence changed and the score was recalculated. No new release drove this move.
Dimensions
12 dimensions, 12 apply to Aztec. Open one to see how it is scored.Access controlscore 50weight 18%
Admin keys, roles, permissions and the checks that guard them.
Economic soundnessscore 50weight 13%
How the economic design holds up under flash loans, MEV, liquidation cascades and bad incentives.
Oracle integrityscore 55weight 13%
How prices reach the protocol, and how hard they are to manipulate or let go stale.
Maturityscore 40weight 12%
Time in production, value secured over time, audits, bounties and incident history.
- Live since
- Not yet measured
- TVL
- Not yet measured
- Audits
- Not yet measured
- Bug bounty
- Not yet measured
Governancescore 50weight 10%
Admin key concentration, timelocks and how upgrades happen.
Cascade exposurescore 40weight 10%
Failures upstream that could spread into the protocol, and the damage if it fails.
Adversarial resiliencescore 50weight 7%
How the code holds up under independent adversarial research.
Compositional riskscore 35weight 5%
External dependencies and the surface where contracts and integrations interact.
Supply chainscore 45weight 4%
Compiler versions, libraries, build reproducibility and proxy patterns.
- Dependabot
- No
Cross-chain messagingscore 35weight 4%
Bridge trust model, sequencer risk, fraud proofs and replay risk.
Liquidity and market structurescore 50weight 2%
Liquidation cascades, holder concentration and exit queues, where positions trade.
Operational securityscore 62weight 2%
Incident response, deployment hygiene, key management and monitoring.
- GitHub scan
- AztecProtocol/aztec-packages on May 20
- Branch protection
- No
- Required reviews
- 0
- Signing ratio
- 64%
- Commits in 90 days
- 50
- PR review ratio
- 83%
- Has CI
- Yes
- CI success rate
- 40%
- Security policy
- Yes
- Deployment hygiene
- 73 of 100
- Development practices
- 45 of 100
- Emergency history
- 75 of 100
- Incident response
- 65 of 100
- Key management
- 70 of 100
- Monitoring
- 40 of 100