How exuralabs/hecate works
Project Type and Purpose
• Hecate is a full-stack data relay service for the Cardano blockchain.
• It connects to an Ogmios-enabled Cardano node, orchestrates historical and real-time data fetches, and forwards that data to downstream systems via Redis or a CLI interface.
• Key use cases: parallel historical syncing, real-time block relay, reorg detection, and optional metrics via Prefect.
File Structure Analysis
• client/ – asynchronous Ogmios WebSocket client and chain/ledger state helpers.
• flows/ – Prefect flow definitions: historical.py, periodic.py; checkpoint.json for dynamic epoch tracking.
• sinks/ – output modules: redis.py and cli.py implementing a common BaseSink interface.
• data/ & constants.py – static CSVs and configuration used by flows.
• models.py – Pydantic or dataclass definitions for message payloads.
• demo.py – ad-hoc script showcasing client capabilities.
• Prefect configuration (prefect.yaml) and project metadata (pyproject.toml).
README Insights
• Emphasis on Prefect for orchestration and Redis/CLI sinks.
• Notes on optional dependencies and deployment.
Detailed Checklist for the Engineer
• Component name exactly as in the code (client/, flows/, sinks/).
• Prefect server/agent separately if used.
• Static data sources (data/epoch_blocks.csv) feeding periodic tasks.
• Reorg detection as a sub-flow or callback loop.
• Concurrency: multiple workers for HistoricalSync.