Ports & Endpoints
Quick reference for all default ports across Pocket Network services. Use this when configuring firewalls, reverse proxies, monitoring, and inter-service communication.
All ports listed are defaults and can be overridden in each service’s configuration. Always check your actual config files for any customizations.
poktroll (Full Node / Validator)
| Port | Protocol | Service | Description |
|---|---|---|---|
| 26656 | TCP | CometBFT P2P | Peer-to-peer communication between nodes |
| 26657 | TCP | CometBFT RPC | JSON-RPC for block queries, tx broadcast, consensus state |
| 26660 | TCP | CometBFT Prometheus | Consensus-layer metrics |
| 9090 | TCP | gRPC | Application-layer queries and transactions |
| 1317 | TCP | REST (LCD) | RESTful API, auto-generated from proto definitions |
| 6060 | TCP | pprof | Go profiling endpoint (debug only) |
RelayMiner (pocket-relay-miner)
| Port | Protocol | Process | Description |
|---|---|---|---|
| 8080 | TCP | Relayer | Relay endpoint (listen_addr) — receives requests from gateways through your TLS proxy |
| 8081 | TCP | Relayer | /health, /ready, and /ready/<service-id> |
| 9090 | TCP | Relayer | Prometheus metrics |
| 9092 | TCP | Miner | Prometheus metrics and /health |
| 6060 | TCP | Relayer, miner | pprof, bound to 127.0.0.1 by default (never expose) |
Internal dependency:
| Port | Protocol | Service | Description |
|---|---|---|---|
| 6379 | TCP | Redis | Every served relay, claim tree, and leader lock (never expose publicly) |
PATH Gateway
| Port | Protocol | Service | Description |
|---|---|---|---|
| 3069 | TCP | Gateway HTTP | User-facing relay endpoint |
| 9090 | TCP | Prometheus | Gateway metrics |
PATH operational endpoints (on the gateway port):
| Path | Description |
|---|---|
/health | Gateway health status |
/ready/<service_id> | Per-service readiness (returns 200 when suppliers are available) |
PATH Components (Helm)
When deploying PATH via Helm, three components run independently:
| Component | Role | Default Port |
|---|---|---|
| PATH | Core gateway — relay routing and QoS | 3069 |
| GUARD | Authentication and access control | Configurable |
| WATCH | Monitoring and observability | Configurable |
Port Conflict Avoidance
When running multiple services on the same machine (e.g., full node + RelayMiner + PATH for development), watch for conflicts on:
- Port 9090 — used by both gRPC (poktroll) and Prometheus (PATH, the RelayMiner’s relayer). Remap one of them.
- Port 6060 — pprof on poktroll and on both RelayMiner processes. Only enable it on the service you’re profiling, and give the relayer and miner different ports if both run on one host.
Monitoring Endpoints Summary
All Prometheus metrics endpoints across services:
| Service | Endpoint | Default |
|---|---|---|
| CometBFT | http://localhost:26660/metrics | Consensus metrics |
| poktroll gRPC | N/A (use Cosmos telemetry) | Application metrics |
| PATH | http://localhost:9090/metrics | Gateway and QoS metrics |
| RelayMiner (relayer) | http://localhost:9090/metrics | Relay metrics |
| RelayMiner (miner) | http://localhost:9092/metrics | Claim and proof metrics |
For a unified monitoring dashboard, point Prometheus at all metrics endpoints and use the Monitoring guide for Grafana dashboard configuration.
Related Pages
- Security — firewall rules and which ports to expose
- RelayMiner Setup — deploy and configure the RelayMiner
- RelayMiner Operations — scaling, sizing, and metrics
- PATH Configuration — PATH YAML config reference
- Monitoring — Prometheus and Grafana setup