How etherspot/skandha works
Main Components Identification
The system consists of several key packages that should be represented as major components:
a) Core Components:
• API Layer (packages/api)
• Executor Engine (packages/executor)
• Node Network Layer (packages/node)
• Database Layer (packages/db)
• Monitoring System (packages/monitoring)
b) Supporting Components:
• CLI Interface (packages/cli)
• Parameter Management (packages/params)
• Type System (packages/types)
• Utility Functions (packages/utils)
┌─ External Interface Layer ─────────────────────┐
• HTTP/RPC API (Port 14337) │
• WebSocket Server │
• ┬─┘
• ↕ │
┌─ Core Processing Layer ───────────────────┐ │
• ┌─ Executor Engine ─┐ ┌─ P2P Network ─┐ │ │
• UserOp │ │ - Discovery │ │ │
• Validation │ │ - Gossip │ │ │
• Bundling │ │ - Sync │ │ │
• Mempool │ └───────────────┘ │ │
• ┘ │ │
• ┬─┘ │
• ↕ │ │
┌─ Storage Layer ──────────────────┐ │ │
• ┌─ RocksDB ─┐ ┌─ Local DB ─┐ │ │ │
• UserOps │ │ - Config │ │ │ │
• State │ │ - Cache │ │ │ │
• ┘ └───────────┘ │ │ │
• ┘ │ │
• ↕ │ │
┌─ Monitoring & Metrics ────────────┐│ │
• Prometheus Metrics ││ │
• Health Checks ││ │
• ┬─┘│ │
• ↕ │ │ │
┌─ External Services ───────────┐│ │ │
• Ethereum RPC Node ││ │ │
• Gas Price Oracles ││ │ │
• Block Explorers ││ │ │
• ┘│ │ │
┌─ Configuration & Control ─────┐│ │ │
• CLI Interface ││ │ │
• Config Management ││ │ │
• ┘│ │ │
• ↓ ↓ ↓
Connection Types
• Double lines: Data flow
Additional Elements
Important details:
• Entry Point contracts (0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789)
• Supported networks (Mumbai, Sepolia, etc.)
• P2P networking details (Discovery v5, Gossip protocol)
• Bundle processing flow
• UserOp validation pipeline