Data Sources & Collection
TODO: Complete Data Sources Documentation
Where EigenWatch gets its data and how we ensure quality.
Required Sections
-
Primary Data Sources
- Beacon chain (validators, attestations, proposals)
- EigenLayer core contracts (operators, delegations, slashing)
- AVS contracts (operator registrations, slashing events)
- MEV relay data (if relevant to operator risk)
- Off-chain indexing services
-
Data Collection Strategy
- Full node vs light client vs service dependency
- Finality requirements (how many blocks before trusting data?)
- Reorg handling
- Data redundancy & validation
-
Data Availability Assumptions
- What happens if a data source goes down?
- Fallback mechanisms
- Impact on risk score accuracy
- User communication strategy
-
Data Validation
- Consistency checks
- Outlier detection
- Cross-source verification
- Confidence levels per data point
-
Data Retention & Archival
- How long is raw data kept?
- Aggregation/summarization strategy for old data
- Historical query capabilities
- Backup & durability
-
Known Limitations
- Data gaps or blind spots
- Bias in data collection (e.g., only on-chain data)
- Latency from event to availability
- Correction/revision policies
Examples
- Beacon chain attestation data latency
- EigenLayer contract update detection time
- Off-chain vs on-chain data reconciliation
Related
Status: NOT STARTED — Requires data engineering specification