RedStone
TEMPEREDOracle Infrastructure · Multi-chain · N/A (oracle) TVL · 5 contracts
Official site: redstone.finance ↗
747
3004756508251000
Confidence63%
Z-Factor0.68
Updated 2026-05-27Public scoreSecurity Profile
Access Control
72
72
Economic Soundness
75
75
Oracle Integrity
78
78
Compositional Risk
60
60
Governance
48
48
Maturity
52
52
Resilience
50
50
Supply Chain
75
75
Op Security
54
54
Cascade Exposure
100
100
Access Ctrl
72
72
Economic
75
75
Oracle
78
78
Compos.
60
60
Govern.
48
48
Maturity
52
52
Resilience
50
50
Supply Ch.
75
75
OpSec
54
54
Cascade
100
100
Min
48
Avg
66
Max
100
Audit History
Peckshield
2023-08
ABDK
2023-05
Quantstamp
2024-01
Bug Bounty Program
$250,000
Max payout on Cantina
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
MethodologyAccess Control
72Weight 18% · 70% confidence
+18Data provider whitelist controlled by team
+18Relayer access for push-based feeds
+18On-demand pull model reduces admin surface
+18Provider authorization centrally managed
Provenance
Economic Soundness
75Weight 13% · 68% confidence
+19Oracle service fee model (not DeFi lending)
+19No direct economic exploit surface in core
+19Data provider staking mechanism
+19Lower economic attack surface than DeFi protocols
Provenance
Oracle Integrity
78Weight 13% · 75% confidence
+26Modular oracle design (Core, Classic, X models)
+26Multi-provider data aggregation
+26EVM calldata-based price injection (innovative but novel)
-22Deduction: calldata model is newer attack surface vs storage
Provenance
Battle-Tested Maturity
52Weight 12% · 60% confidence
+13Live since early 2023 (~28 months)
+13Growing adoption but still establishing track record
+13No known exploit but limited stress history
+13Z-factor: 0.824
Provenance
Governance & Upgradeability
48Weight 10% · 60% confidence
+16Team-controlled protocol parameters
-52No on-chain governance mechanism
+16Data provider set controlled centrally
+16Limited decentralization of oracle operations
Provenance
Adversarial Resilienceredacted
50Weight 10% · 30% confidence
- 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
Provenance
Operational Security
54Weight 10% · 35% confidence
-46No branch protection detected
+14No CI/CD pipeline detected
+14Moderate development (17 commits/month)
+14No CI pipeline for deployment verification
Provenance
Compositional Risk
60Weight 5% · 65% confidence
+15Oracle consumed by many DeFi protocols
+15Multi-chain deployment increases composition surface
+15Calldata injection model means consumer must integrate correctly
+15Integration errors can cause downstream failures
Provenance
Cascade Exposure
100Weight 5% · 55% confidence
+33Appears in 1 cross-protocol cascade chain(s)
+33Member of 2 dependency cluster(s)
+33Source: cross_protocol_composition.json dependency analysis
Provenance
Supply Chain
75Weight 4% · 70% confidence
+19Modern Solidity (0.8.x)
+19Standard dependencies
+19Multi-chain deployment infrastructure
+19Calldata injection adds unique supply chain element
Provenance
Top Score Drivers
Dimensions with the greatest marginal impact on BRI.
Battle-Tested Maturity
52+36.5 potential
Live since early 2023 (~28 months)
Governance & Upgradeability
48+34 potential
No on-chain governance mechanism
Adversarial Resilience
50+32.1 potential
Operational Security
54+28.4 potential
No branch protection detected
Access Control
72+27.2 potential
Data provider whitelist controlled by team
Adversarial Risk Signals
Publicly verifiable security posture indicators.
Disclosure HistoryNot Assessed
Remediation VelocityNot Assessed
Bug Bounty ProgramNot Assessed
Audit CoverageNot Assessed
Incident HistoryNot Assessed
methodology v2.1formula v1.1weights v1.1evidence sha256:sha256:2...
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
Read Score
registry.getScore("redstone")Reduce exploitable risk
Continuous adversarial analysis, vulnerability detection, and verified reassessment.
Embed this score
Live, updates automatically. Free for any site. Click-through links open the full report on BlackHart.
Style
Theme
Format
Preview
Copy iframe code
<iframe
src="https://blackhart.io/embed/oracle/redstone?variant=card&theme=dark"
title="BlackHart Risk Index: RedStone"
width="340"
height="290"
frameborder="0"
loading="lazy"
style="border:0; max-width:100%;"
></iframe>