Skip to content

Features and Functionality Features and Functionality

Jump to bottom
dev-mondoshawan edited this page Apr 15, 2026 · 1 revision

Features & Functionality

**Referenced Files in This Document** - [backend/src/routes/network.js](file://backend/src/routes/network.js) - [backend/src/routes/rpc.js](file://backend/src/routes/rpc.js) - [backend/src/routes/validators.js](file://backend/src/routes/validators.js) - [backend/src/routes/epoch.js](file://backend/src/routes/epoch.js) - [backend/src/services/solanaRpc.js](file://backend/src/services/solanaRpc.js) - [backend/src/services/rpcProber.js](file://backend/src/services/rpcProber.js) - [backend/src/services/validatorsApp.js](file://backend/src/services/validatorsApp.js) - [backend/src/models/queries.js](file://backend/src/models/queries.js) - [backend/src/models/redis.js](file://backend/src/models/redis.js) - [backend/src/models/cacheKeys.js](file://backend/src/models/cacheKeys.js) - [backend/src/websocket/index.js](file://backend/src/websocket/index.js) - [frontend/src/pages/Dashboard.jsx](file://frontend/src/pages/Dashboard.jsx) - [frontend/src/components/dashboard/TpsCard.jsx](file://frontend/src/components/dashboard/TpsCard.jsx) - [frontend/src/components/dashboard/SlotLatencyCard.jsx](file://frontend/src/components/dashboard/SlotLatencyCard.jsx) - [frontend/src/components/dashboard/EpochProgressCard.jsx](file://frontend/src/components/dashboard/EpochProgressCard.jsx) - [frontend/src/services/networkApi.js](file://frontend/src/services/networkApi.js) - [frontend/src/pages/RpcHealth.jsx](file://frontend/src/pages/RpcHealth.jsx) - [frontend/src/components/rpc/RpcProviderTable.jsx](file://frontend/src/components/rpc/RpcProviderTable.jsx) - [frontend/src/services/rpcApi.js](file://frontend/src/services/rpcApi.js) - [frontend/src/pages/Validators.jsx](file://frontend/src/pages/Validators.jsx) - [frontend/src/components/validators/ValidatorTable.jsx](file://frontend/src/components/validators/ValidatorTable.jsx) - [frontend/src/pages/DataCenterMap.jsx](file://frontend/src/pages/DataCenterMap.jsx) - [frontend/src/pages/MevTracker.jsx](file://frontend/src/pages/MevTracker.jsx) - [frontend/src/pages/Alerts.jsx](file://frontend/src/pages/Alerts.jsx)

Table of Contents

  1. Introduction
  2. Project Structure
  3. Core Components
  4. Architecture Overview
  5. Detailed Component Analysis
  6. Dependency Analysis
  7. Performance Considerations
  8. Troubleshooting Guide
  9. Conclusion
  10. Appendices

Introduction

This document describes InfraWatch’s core features and functionality as implemented in the repository. It covers:

  • Network health dashboard: TPS monitoring, slot latency tracking, epoch progress visualization, congestion scoring, and confirmation time metrics.
  • RPC provider monitoring: health checks, performance statistics, and automated recommendations.
  • Validator health tracking: performance scoring, delinquency monitoring, and commission change indicators.
  • MEV exposure monitoring for Jito validators and tip floor tracking.
  • Data center risk assessment via geographic distribution mapping and concentration risk calculations.
  • Alert system configuration and notification management.

The backend exposes REST endpoints and caches results for efficient frontend consumption. The frontend renders dashboards and tables with real-time updates and sorting capabilities.

Project Structure

The application follows a split monorepo-like structure:

  • Backend: Express routes, services, caching, and database queries.
  • Frontend: React pages, components, stores, and API service wrappers.
graph TB
subgraph "Backend"
R1["Routes<br/>network.js, rpc.js, validators.js, epoch.js"]
S1["Services<br/>solanaRpc.js, rpcProber.js, validatorsApp.js"]
M1["Models<br/>queries.js, redis.js, cacheKeys.js"]
WS["WebSocket<br/>websocket/index.js"]
end
subgraph "Frontend"
P1["Pages<br/>Dashboard.jsx, RpcHealth.jsx, Validators.jsx,<br/>DataCenterMap.jsx, MevTracker.jsx, Alerts.jsx"]
C1["Components<br/>Dashboard Cards, RPC Table, Validator Table"]
API["Services<br/>networkApi.js, rpcApi.js"]
end
P1 --> API
API --> R1
R1 --> S1
R1 --> M1
S1 --> M1
WS --> P1
C1 --> P1
Loading

Diagram sources

  • backend/src/routes/network.js:1-135
  • backend/src/routes/rpc.js:1-135
  • backend/src/routes/validators.js:1-112
  • backend/src/routes/epoch.js:1-62
  • backend/src/services/solanaRpc.js:1-340
  • backend/src/services/rpcProber.js
  • backend/src/services/validatorsApp.js
  • backend/src/models/queries.js
  • backend/src/models/redis.js
  • backend/src/models/cacheKeys.js
  • backend/src/websocket/index.js
  • frontend/src/pages/Dashboard.jsx:1-84
  • frontend/src/pages/RpcHealth.jsx:1-153
  • frontend/src/pages/Validators.jsx:1-179
  • frontend/src/pages/DataCenterMap.jsx
  • frontend/src/pages/MevTracker.jsx
  • frontend/src/pages/Alerts.jsx
  • frontend/src/services/networkApi.js:1-6
  • frontend/src/services/rpcApi.js:1-7

Section sources

  • backend/src/routes/network.js:1-135
  • backend/src/routes/rpc.js:1-135
  • backend/src/routes/validators.js:1-112
  • backend/src/routes/epoch.js:1-62
  • backend/src/services/solanaRpc.js:1-340
  • frontend/src/pages/Dashboard.jsx:1-84
  • frontend/src/pages/RpcHealth.jsx:1-153
  • frontend/src/pages/Validators.jsx:1-179

Core Components

  • Network dashboard endpoints provide current network status and historical charts for TPS, epoch progress, and congestion.
  • RPC monitoring aggregates live health and rolling statistics, and surfaces a recommended provider.
  • Validator rankings expose top validators with scores, stake, commission, skip rate, and delinquency status.
  • Epoch info is fetched from Solana RPC and cached for quick rendering.
  • WebSocket support enables real-time updates to the dashboard.

Section sources

  • backend/src/routes/network.js:17-79
  • backend/src/routes/network.js:85-132
  • backend/src/routes/rpc.js:17-88
  • backend/src/routes/rpc.js:94-132
  • backend/src/routes/validators.js:17-46
  • backend/src/routes/validators.js:52-109
  • backend/src/routes/epoch.js:16-59
  • backend/src/services/solanaRpc.js:275-328
  • backend/src/websocket/index.js

Architecture Overview

The backend orchestrates data collection from Solana RPC and external services, persists and caches results, and serves them via REST endpoints. The frontend consumes these endpoints, renders dashboards, and refreshes periodically.

sequenceDiagram
participant FE as "Frontend Pages"
participant API as "Express Routes"
participant SVC as "Services"
participant DB as "Queries/DB"
participant RC as "Redis Cache"
participant RPC as "Solana RPC"
FE->>API : "GET /api/network/current"
API->>RC : "getCache(NETWORK_CURRENT)"
alt "Cache hit"
RC-->>API : "Snapshot"
else "Cache miss"
API->>DB : "getLatestNetworkSnapshot()"
DB-->>API : "Snapshot"
end
API->>RPC : "getRecentPerformanceSamples/getSlot/getEpochInfo"
RPC-->>API : "Metrics"
API-->>FE : "JSON response"
FE->>API : "GET /api/rpc/status"
API->>RC : "getCache(RPC_LATEST)"
alt "Cache hit"
RC-->>API : "Providers"
else "Cache miss"
API->>DB : "getRpcLatestByProvider()"
DB-->>API : "Providers"
end
API->>SVC : "getAllProviderStats(), getBestProvider()"
SVC-->>API : "Rolling stats + recommendation"
API-->>FE : "Providers + recommendation"
Loading

Diagram sources

  • backend/src/routes/network.js:17-79
  • backend/src/routes/rpc.js:17-88
  • backend/src/services/solanaRpc.js:40-156
  • backend/src/models/redis.js
  • backend/src/models/queries.js

Detailed Component Analysis

Network Health Dashboard

The dashboard displays:

  • TPS and a 30-point TPS history chart.
  • Slot latency with a health threshold.
  • Epoch progress with ETA and slot counters.
  • Confirmation time and congestion score derived from TPS, latency, and priority fees.
  • Delinquent and active validator counts.
flowchart TD
Start(["Fetch Network Data"]) --> Current["GET /api/network/current"]
Current --> CacheCheck{"Cache hit?"}
CacheCheck --> |Yes| UseCache["Return cached snapshot"]
CacheCheck --> |No| QueryDB["Query latest snapshot"]
QueryDB --> SnapshotReady["Assemble metrics:<br/>TPS, slot latency, epoch, delinquency,<br/>confirmation time, congestion score"]
SnapshotReady --> ReturnCurrent["Return JSON"]
Start --> History["GET /api/network/history?range"]
History --> HistCacheCheck{"Cache hit?"}
HistCacheCheck --> |Yes| UseHistCache["Return cached history"]
HistCacheCheck --> |No| QueryHistDB["Query history by range"]
QueryHistDB --> CacheHist["Cache history"]
CacheHist --> ReturnHist["Return JSON"]
Loading

Diagram sources

  • backend/src/routes/network.js:17-79
  • backend/src/routes/network.js:85-132
  • backend/src/services/solanaRpc.js:275-328

Section sources

  • frontend/src/pages/Dashboard.jsx:19-83
  • frontend/src/components/dashboard/TpsCard.jsx:14-56
  • frontend/src/components/dashboard/SlotLatencyCard.jsx:12-28
  • frontend/src/components/dashboard/EpochProgressCard.jsx:5-73
  • frontend/src/services/networkApi.js:1-6
  • backend/src/services/solanaRpc.js:228-268

RPC Provider Monitoring

The RPC health page shows:

  • Live health status, latency, and error messages per provider.
  • Rolling statistics: p50/p95/p99 latency, uptime percentage, total checks, and last incident.
  • Provider categorization (Premium/Public) and a recommended provider.
sequenceDiagram
participant FE as "RpcHealth Page"
participant API as "/api/rpc/status"
participant RC as "Redis"
participant DB as "Queries"
participant RP as "rpcProber"
FE->>API : "GET /api/rpc/status"
API->>RC : "getCache(RPC_LATEST)"
alt "Cache exists"
RC-->>API : "providers"
else "No cache"
API->>DB : "getRpcLatestByProvider()"
DB-->>API : "providers"
end
API->>RP : "getAllProviderStats()"
RP-->>API : "rolling stats"
API->>RP : "getBestProvider()"
RP-->>API : "best provider"
API-->>FE : "{providers, recommendation}"
Loading

Diagram sources

  • backend/src/routes/rpc.js:17-88
  • backend/src/services/rpcProber.js
  • backend/src/models/redis.js
  • backend/src/models/queries.js

Section sources

  • frontend/src/pages/RpcHealth.jsx:8-152
  • frontend/src/components/rpc/RpcProviderTable.jsx:39-176
  • frontend/src/services/rpcApi.js:1-7
  • backend/src/routes/rpc.js:94-132

Validator Health Tracking

The validators page presents:

  • Top validators ranked by score with stake, commission, skip rate, software version, and data center.
  • Delinquency status and selection of a validator for detailed view.
  • Sorting by name, score, stake, commission, skip rate, and others.
sequenceDiagram
participant FE as "Validators Page"
participant API as "/api/validators/top"
participant RC as "Redis"
participant DB as "Queries"
participant VA as "validatorsApp"
FE->>API : "GET /api/validators/top?limit"
API->>RC : "getCache(VALIDATORS_TOP100)"
alt "Cache hit"
RC-->>API : "subset"
else "Cache miss"
API->>DB : "getTopValidators(limit)"
DB-->>API : "validators"
end
API-->>FE : "Top validators"
FE->>API : "GET /api/validators/ : votePubkey"
API->>RC : "getCache(VALIDATOR_DETAIL)"
alt "Cache hit"
RC-->>API : "validator"
else "Cache miss"
API->>VA : "getValidatorDetail(votePubkey)"
VA-->>API : "validator"
alt "Fallback"
API->>DB : "getValidatorByPubkey(votePubkey)"
DB-->>API : "validator"
end
end
API-->>FE : "Validator detail"
Loading

Diagram sources

  • backend/src/routes/validators.js:17-46
  • backend/src/routes/validators.js:52-109
  • backend/src/services/validatorsApp.js
  • backend/src/models/redis.js
  • backend/src/models/queries.js

Section sources

  • frontend/src/pages/Validators.jsx:8-178
  • frontend/src/components/validators/ValidatorTable.jsx:35-201
  • backend/src/routes/validators.js:17-46
  • backend/src/routes/validators.js:52-109

Epoch Progress Visualization

Epoch information is fetched from Solana RPC and cached. The frontend renders epoch number, progress percentage, ETA, and slot counters.

sequenceDiagram
participant FE as "Dashboard"
participant API as "/api/epoch/current"
participant RC as "Redis"
participant SR as "solanaRpc"
FE->>API : "GET /api/epoch/current"
API->>RC : "getCache(EPOCH_INFO)"
alt "Cache hit"
RC-->>API : "epoch info"
else "Cache miss"
API->>SR : "getEpochInfo()"
SR-->>API : "epoch info"
API->>RC : "setCache(EPOCH_INFO)"
end
API-->>FE : "{epoch, progress, eta, slots...}"
Loading

Diagram sources

  • backend/src/routes/epoch.js:16-59
  • backend/src/services/solanaRpc.js:124-156
  • backend/src/models/redis.js

Section sources

  • frontend/src/pages/Dashboard.jsx:32-40
  • frontend/src/components/dashboard/EpochProgressCard.jsx:5-73
  • backend/src/routes/epoch.js:16-59

MEV Exposure Monitoring and Tip Floor Tracking

The MEV tracker page provides visibility into Jito-related metrics and tip floor trends. It integrates with external MEV data sources and displays relevant signals for validator operators.

flowchart TD
Start(["MEV Tracker Page"]) --> Load["Load MEV metrics"]
Load --> Render["Render charts and signals"]
Render --> Insights["Exposure and tip floor insights"]
Insights --> End(["Operator guidance"])
Loading

Section sources

  • frontend/src/pages/MevTracker.jsx

Data Center Risk Assessment

The data center map page visualizes geographic distribution of validators and computes concentration risk. It helps operators diversify infrastructure to reduce geographic risk.

flowchart TD
Start(["Data Center Map"]) --> Geo["Collect validator geo locations"]
Geo --> Dist["Compute geographic distribution"]
Dist --> Risk["Calculate concentration risk"]
Risk --> Visualize["Render map and risk metrics"]
Visualize --> End(["Risk insights"])
Loading

Section sources

  • frontend/src/pages/DataCenterMap.jsx

Alert System Configuration and Notification Management

The alerts page allows configuring and managing notifications for critical events across network, RPC, and validator domains. Operators can subscribe to specific conditions and receive timely updates.

flowchart TD
Start(["Alerts Page"]) --> Config["Configure alert rules"]
Config --> Subscribe["Subscribe to notifications"]
Subscribe --> Manage["Manage notification channels"]
Manage --> Test["Test and validate alerts"]
Test --> End(["Active monitoring"])
Loading

Section sources

  • frontend/src/pages/Alerts.jsx

Dependency Analysis

The backend components depend on services and models for data retrieval and caching. The frontend depends on route endpoints and stores for state management.

graph LR
FE_Dash["Dashboard.jsx"] --> API_N["networkApi.js"]
FE_RPC["RpcHealth.jsx"] --> API_R["rpcApi.js"]
FE_Val["Validators.jsx"] --> API_V["validatorApi.js"]
API_N --> R_NET["routes/network.js"]
API_R --> R_RPC["routes/rpc.js"]
API_V --> R_VAL["routes/validators.js"]
R_EPO["routes/epoch.js"] --> SRPC["solanaRpc.js"]
R_NET --> S_SVC["solanaRpc.js"]
R_RPC --> RP_PROBE["rpcProber.js"]
R_VAL --> V_APP["validatorsApp.js"]
R_NET --> Q["queries.js"]
R_RPC --> Q
R_VAL --> Q
R_EPO --> Q
R_NET --> REDIS["redis.js"]
R_RPC --> REDIS
R_VAL --> REDIS
R_EPO --> REDIS
Loading

Diagram sources

  • frontend/src/pages/Dashboard.jsx:1-84
  • frontend/src/pages/RpcHealth.jsx:1-153
  • frontend/src/pages/Validators.jsx:1-179
  • frontend/src/services/networkApi.js:1-6
  • frontend/src/services/rpcApi.js:1-7
  • backend/src/routes/network.js:1-135
  • backend/src/routes/rpc.js:1-135
  • backend/src/routes/validators.js:1-112
  • backend/src/routes/epoch.js:1-62
  • backend/src/services/solanaRpc.js:1-340
  • backend/src/services/rpcProber.js
  • backend/src/services/validatorsApp.js
  • backend/src/models/queries.js
  • backend/src/models/redis.js

Section sources

  • backend/src/models/cacheKeys.js
  • backend/src/websocket/index.js

Performance Considerations

  • Caching: Redis keys are used for current network status, RPC latest, validator top lists, and epoch info to minimize RPC and DB load.
  • Parallel collection: Network snapshots aggregate multiple RPC calls concurrently.
  • Rolling statistics: RPC prober maintains windowed stats for latency percentiles and uptime.
  • Frontend polling: Pages poll endpoints at intervals to balance freshness and load.

[No sources needed since this section provides general guidance]

Troubleshooting Guide

Common issues and remedies:

  • No network data available: The network route returns a 503 when startup data is missing; retry after initialization completes.
  • Redis failures: Routes fall back to DB queries; cache set failures are logged and do not block responses.
  • RPC unavailability: Epoch and network routes rely on Solana RPC; errors are handled gracefully with defaults.
  • Validator detail not found: Route returns 404 when no record is present; check vote public key and external data sync.

Section sources

  • backend/src/routes/network.js:44-61
  • backend/src/routes/network.js:110-126
  • backend/src/routes/epoch.js:37-55
  • backend/src/routes/validators.js:82-96

Conclusion

InfraWatch delivers a comprehensive observability platform for Solana infrastructure. The backend efficiently collects and caches network, RPC, and validator data, while the frontend provides actionable dashboards and tables. The platform supports operational excellence through real-time monitoring, recommendations, and alerting.

[No sources needed since this section summarizes without analyzing specific files]

Appendices

  • Real-time updates: WebSocket integration enhances live data delivery to the dashboard.
  • Provider categories: Premium vs Public categorization aids quick triage of provider quality.
  • Sorting and filtering: Frontend components enable operator-driven exploration of RPC and validator datasets.

Section sources

  • backend/src/websocket/index.js
  • frontend/src/components/rpc/RpcProviderTable.jsx:5-14
  • frontend/src/pages/RpcHealth.jsx:41-77
  • frontend/src/pages/Validators.jsx:53-88

InfraWatch Wiki

Getting Started

Architecture

API Reference

Backend Architecture

Background Jobs & Data Collection

Data Persistence Layer

Routing System

Service Layer Architecture

Frontend Architecture

Features & Functionality

Clone this wiki locally