Concrete Protocol
TEMPEREDYield Vault · Ethereum · $100M+ TVL · 10 contracts
Public risk assessment — scores are produced with the same methodology as monitored protocols
Security Profile
68
62
70
55
42
32
50
72
62
100
68
62
70
55
42
32
50
72
62
100
Audit History
Bug Bounty Program
Assessment
Very new yield optimization protocol with minimal battle testing. Extremely low maturity (Z=0.143, D6=32) is the dominant risk factor. Governance centralization (D5=42) and unproven economics compound the risk. Score reflects high uncertainty.
Dimension Breakdown
How scores work →- Vault-based architecture with strategist controls
- Admin roles for vault configuration and strategy allocation
- Deposit/withdrawal access through vault interface
- Limited public documentation on permission model
- Yield optimization via strategy rotation
- Economic model unproven at scale
- Fee structure not yet stress-tested
- Token incentives may distort real yield
- Standard oracle dependencies for asset pricing
- Strategy valuation relies on underlying protocol oracles
- Limited information on oracle failure handling
- New protocol = oracle integration maturity unknown
- Mainnet since Q1 2026 (~3 months)
- Extremely new protocol
- Limited TVL and usage history
- Initial audits completed but minimal battle testing
- Z-factor: 0.143
- Team-controlled governance (early stage)
- No meaningful decentralization yet
- Vault parameters controlled by admin
- Governance structure not yet established
- Maximum resilience under independent adversarial testing
- Comprehensive security coverage across all attack surfaces
- Mature codebase with extensive battle testing
- No validated adversarial findings — score set to neutral baseline
- New team, operational track record unproven
- Strategy management requires active operations
- Monitoring infrastructure maturity unknown
- Early-stage operational procedures
- Yield optimization composes across DeFi protocols
- Strategy allocation creates multi-protocol exposure
- New strategies may add untested composition paths
- Bounded by vault architecture but wide strategy surface
- Member of 1 dependency cluster(s)
- No cross-protocol cascade exposure detected
- Score: 100/100 (higher = more isolated from systemic risk)
- Source: cross_protocol_composition.json dependency analysis
- Standard Solidity dependencies
- Vault pattern from established libraries
- Strategy contracts add dependency surface
- New codebase = limited dependency audit depth
Risk Drivers
Primary risk factors driving this score, ordered by severity.
Adversarial Risk Signals
Observable security posture indicators. These signals reflect publicly verifiable information and responsible disclosure outcomes. No specific vulnerability details are exposed.
Score History & Verification
Score provenance tracking begins with the next reassessment.
On-Chain Data
- Protocol Slug
- "concrete"
- Oracle
- BRORegistry (Base)
- Evidence
- IPFS (pinned)
- Staleness Threshold
- 24 hours
registry.getScore("concrete")Reduce exploitable risk
BlackHart Monitoring provides continuous adversarial analysis, vulnerability detection, remediation support, and verified reassessment when your risk posture improves.