How helium/oracles works
Overall Project Purpose and Type
• This is a modular, multi-service system that is part of the Helium “Oracles” project. It’s clearly built as a distributed set of microservices handling both Mobile and IoT data flows.
File Structure
• There are many modules such as boost_manager, file_store, ingest, iot_config, and several mobile and IoT related libraries. This indicates the project is organized as multiple microservices or components that perform very specific tasks (e.g., reward calculation, data ingestion, price tracking, etc.).
• Migration scripts, settings templates, and tests all exist in each module, meaning that each component can be separately deployed and scaled.
• There is also tooling for tracing, metrics, and orchestration (e.g., custom_tracing, task_manager) that are important from an observability and management perspective.
Main Components and Their Interactions
• For Mobile:
• Mobile Ingestor: Gathers heartbeats, speedtests, data transfer sessions, and other mobile data.
• Mobile Verifier: Validates incoming mobile data and calculates rewards.
• Mobile Packet Verifier: Handles data transfer and burns DC on Solana.
• Mobile Price: Records price data (e.g., via Pyth) and communicates with Solana.
• Mobile Config: Acts as a central access point to on-chain data and stores pubkeys.
• Mobile Reward Index: Aggregates computed rewards that are then written into an external (foundation-owned) database.
• For IoT:
• IoT Ingestor: Gathers packets from hotspots, beacons, witnesses, and maintains long-lived gRPC streams.
• IoT Verifier: Validates IoT data, calculates rewards, and processes associated entropy.
• IoT Config: Provides settings for on-chain data and stores organization and routing information.
• Helium Packet Router: Routes packets between hotspots and the Helium LNS.
• IoT Packet Verifier: Burns DC for IoT data transfers.
• IoT Entropy: Generates system entropy used by other services.
• IoT Reward Index: Aggregates IoT rewards and writes them to the foundation-owned database.
• External Components:
• External Databases: Two types are evident – one for initial configuration/data population (Foundation owned db populated by Helium) and one that stores reward totals.
• Solana is a key external blockchain system, and its role is shown for Mobile Price and Packet Verifiers.
Technical Stack and Architectural Patterns
• The project is built in Rust with a microservices approach, where each service has its own module and deployment pipeline.
• Out configuration management components (like Mobile Config and IoT Config) which are central for controlling service behavior.
• If needed, show testing layers or migration processes as side notes to emphasize robust deployment practices.