System Architecture

High-Level Diagram

1Exchange Feeds → Feature Engine → AI Policy → Signal Payload
2                         |                |
3                         |                └── Publish (Telegram/Web/API @ T₀)
4                         └── Commit (hash) → PoP Contract @ T₀
5                                             └── Reveal payload @ T₁
6                                                      └── Public Verification & Analytics
7Analytics

Components

• Connectors: Resilient WS/REST to exchanges; clock sync; backfill.
• Feature Engine: OB imbalance, spread, delta, absorption/sweeps, regimes.
• AI Policy & Rules: Blends microstructure signals with AI risk calibration (entries/TP/SL/confidence).
• Signal Orchestrator: Finalizes payload, computes hash, commits on-chain, publishes, and schedules reveal.
• PoP Contract: Stores commits (hash/merkle root + meta), verifies reveals, emits events.
• Storage: Redis (hot), ClickHouse/S3 (cold), IPFS (payload archival, CID anchored on-chain).
• Delivery: Telegram bot, Web UI, API/Webhooks.
• Verification: Explorer + SDK/CLI for hash checks and Merkle proofs.

Data Flow

1. 1.
   Ingest 5m/15m/1h candles, trades, L2 depth.
2. 2.
   Compute features → generate signal payload.
3. 3.
   Commit hash (or batch root) on-chain and Publish readable call.
4. 4.
   Reveal payload later within time-window; indexer marks Verified.