RedStone
DAMASCUSOracle Infrastructure · Multi-chain · N/A (oracle) TVL · 5 contracts
Public risk assessment — scores are produced with the same methodology as monitored protocols
Security Profile
72
75
78
60
48
52
50
75
65
100
72
75
78
60
48
52
50
75
65
100
Audit History
Bug Bounty Program
Assessment
Modular oracle protocol competing with Chainlink (28 months). D5 low (48) for centralized governance. D6 moderate (52) for limited maturity. Innovative calldata-based model but newer attack surface. D4 low (60) as oracle failures cascade to consumers.
Dimension Breakdown
How scores work →- Data provider whitelist controlled by team
- Relayer access for push-based feeds
- On-demand pull model reduces admin surface
- Provider authorization centrally managed
- Oracle service fee model (not DeFi lending)
- No direct economic exploit surface in core
- Data provider staking mechanism
- Lower economic attack surface than DeFi protocols
- Modular oracle design (Core, Classic, X models)
- Multi-provider data aggregation
- EVM calldata-based price injection (innovative but novel)
- Deduction: calldata model is newer attack surface vs storage
- Live since early 2023 (~28 months)
- Growing adoption but still establishing track record
- No known exploit but limited stress history
- Z-factor: 0.824
- Team-controlled protocol parameters
- No on-chain governance mechanism
- Data provider set controlled centrally
- Limited decentralization of oracle operations
- 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
- Professional team with oracle expertise
- Multi-chain operational complexity
- Data provider monitoring infrastructure
- Limited public incident response documentation
- Oracle consumed by many DeFi protocols
- Multi-chain deployment increases composition surface
- Calldata injection model means consumer must integrate correctly
- Integration errors can cause downstream failures
- Appears in 1 cross-protocol cascade chain(s)
- Member of 2 dependency cluster(s)
- Score: 100/100 (higher = more isolated from systemic risk)
- Source: cross_protocol_composition.json dependency analysis
- Modern Solidity (0.8.x)
- Standard dependencies
- Multi-chain deployment infrastructure
- Calldata injection adds unique supply chain element
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
- "redstone"
- Oracle
- BRORegistry (Base)
- Evidence
- IPFS (pinned)
- Staleness Threshold
- 24 hours
registry.getScore("redstone")Reduce exploitable risk
BlackHart Monitoring provides continuous adversarial analysis, vulnerability detection, remediation support, and verified reassessment when your risk posture improves.