How 0xintuition/intuition-rs works
Project type and purpose
• This is a full-stack Rust workspace (“intuition-rust”) that implements a blockchain-event processing pipeline.
• It ingests on-chain data (via Substreams or Envio), decodes and enriches it with resolvers and IPFS uploads, stores it in Postgres via Hasura, and exposes it through GraphQL, REST, and a TUI/CLI.
Top-level components
• Data Ingestion
• substreams-sink (Substreams event consumer)
• envio-indexer (Envio-based on-chain indexer)
• Consumers
• RAW, DECODED, RESOLVER — each reads from AWS SQS queues
• histoflux (streams historical + live DB events back to SQS)
• Data Store & API
• Hasura + PostgreSQL (metadata, migrations, GraphQL)
• consumer-api (refetch API for atoms)
• Auxiliary Services
• rpc-proxy (caches eth_call results for EthMultiVault)
• image-guard (uploads/validates images to IPFS/Pinata)
• rpc providers (Alchemy, local Geth node)
• external tokens/services (Pinata, HuggingFace, Substreams API, AWS SQS)
• Client Interfaces
• cli (TUI CLI)
• local Docker Compose / Minikube / EKS orchestrations
Data flow and relationships
• On-chain → substreams-sink or envio-indexer → writes to Postgres
• Postgres ← Hasura migrations & config applied
• histoflux tail DB changes → sends to SQS
• RAW consumer reads raw logs from SQS, decodes → writes enriched data back to Postgres
• DECODED consumer reads from decoded-queue, enriches or parses → Postgres
• RESOLVER consumer reads from resolver-queue, resolves ENS/IPFS references → Postgres
• image-guard receives HTTP uploads → IPFS (via Pinata) → metadata written to Postgres
• rpc-proxy fronts Ethereum RPC calls → caches currentSharePrice → returns JSON RPC
• consumer-api fronts refetch requests → queries Postgres and/or RPC-proxy
• Hasura GraphQL service sits atop Postgres → exposes GraphQL endpoint
• cli app queries GraphQL or consumer-api for data display
Architectural patterns
• Microservices: each crate compiles to its own container/microservice.
• Event-driven: uses SQS for decoupling consumers.
• CQRS/Streaming: histoflux streams DB events to SQS; consumers update write models.
• API Layer: Hasura for GraphQL, custom REST via consumer-api and rpc-proxy.
• Feature-flagged behavior: consumer supports local vs. remote via Cargo features.
Technologies & frameworks
• Rust crates managed in a Cargo workspace.
• Docker / docker-compose for local development.
• AWS SQS for queueing.
• Envoy vs. Substreams ingestion.
• Hasura CLI + metadata for GraphQL layer.
• Kubernetes manifests (ArgoCD, Kustomize) for EKS or Minikube.
• PostgreSQL as primary datastore.
• External: Alchemy nodes, Pinata IPFS gateway, HuggingFace, Substreams API.