erigon-network-ports
A reference guide for Erigon network ports to prevent port conflicts when running multiple instances.
Install
mkdir -p .claude/skills/erigon-network-ports && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4599" && unzip -o skill.zip -d .claude/skills/erigon-network-ports && rm skill.zipInstalls to .claude/skills/erigon-network-ports
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Reference for all Erigon network ports. Use this when running multiple Erigon instances to avoid port conflicts. Lists every CLI flag that binds a port, its default value, and the protocol used.Key capabilities
- →Identify network ports for Erigon instances
- →Configure custom ports for multiple instances
- →Map protocols to specific CLI flags
- →Debug address already in use errors
How it works
It provides a reference table of CLI flags and default ports that must be modified to prevent conflicts when running multiple Erigon nodes on one machine.
Inputs & outputs
When to use erigon-network-ports
- →Configuring multiple Erigon instances on one machine
- →Debugging 'bind: address already in use' errors
- →Mapping network ports for custom Docker deployments
About this skill
Erigon Port Reference
When running multiple Erigon instances on the same machine, every listening port must be unique per instance. Erigon will fail at startup if any port is already in use, reporting bind: address already in use.
All Ports That Must Be Changed
| CLI Flag | Default | Protocol | Description |
|---|---|---|---|
--private.api.addr | 127.0.0.1:9090 | TCP (gRPC) | Internal gRPC API for component communication (txpool, rpcdaemon, sentry, downloader) |
--http.port | 8545 | TCP | JSON-RPC HTTP server |
--authrpc.port | 8551 | TCP | Engine API (consensus layer auth RPC) |
--ws.port | 8546 | TCP | WebSocket RPC server |
--torrent.port | 42069 | TCP+UDP | BitTorrent protocol for snapshot downloads |
--port | 30303 | TCP+UDP | DevP2P network listening port (all eth versions multiplexed) |
--caplin.discovery.port | 4000 | UDP | Caplin consensus DISCV5 discovery |
--caplin.discovery.tcpport | 4001 | TCP | Caplin consensus DISCV5 TCP |
--sentinel.port | 7777 | TCP | Sentinel (consensus p2p service) |
--beacon.api.port | 5555 | TCP | Beacon Chain REST API |
--mcp.port | 8553 | TCP | MCP (Model Context Protocol) RPC server |
Conditional Ports (only if enabled)
| CLI Flag | Default | Protocol | Description |
|---|---|---|---|
--pprof.port | 6060 | TCP | Go pprof profiling HTTP server (requires --pprof) |
--metrics.port | 6061 | TCP | Prometheus metrics HTTP server (requires --metrics) |
Example: Two Instances
Instance 1 (using defaults):
./build/bin/erigon --datadir /path/to/datadir1
Instance 2 (all ports offset by +100):
./build/bin/erigon --datadir /path/to/datadir2 \
--private.api.addr=127.0.0.1:9190 \
--http.port=8645 \
--authrpc.port=8651 \
--ws.port=8646 \
--torrent.port=42169 \
--port=30403 \
--caplin.discovery.port=4100 \
--caplin.discovery.tcpport=4101 \
--sentinel.port=7877 \
--beacon.api.port=5655 \
--mcp.port=8653
Notes
--private.api.addrtakes a fullhost:portvalue, not just a port number.- The torrent port binds on both TCP and UDP; it is typically the first port conflict encountered at startup.
- If
--pprofor--metricsare enabled on both instances, their ports must also differ.
When not to use it
- →When running only a single Erigon instance with default settings
Limitations
- →Requires manual port offset configuration
- →Does not automatically manage port allocation
How it compares
It provides a centralized reference for all bindable ports, whereas manual debugging requires checking individual service documentation.
Compared to similar skills
erigon-network-ports side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| erigon-network-ports (this skill) | 2 | 2mo | Review | Beginner |
| turborepo | 61 | 2mo | Review | Intermediate |
| applescript | 28 | 8mo | Review | Advanced |
| cloudflare-manager | 25 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by erigontech
View all by erigontech →You might also like
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
applescript
martinholovsky
Expert in AppleScript and JavaScript for Automation (JXA) for macOS system scripting. Specializes in secure script execution, application automation, and system integration. HIGH-RISK skill due to shell command execution and system-wide control capabilities.
cloudflare-manager
qdhenry
Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
railway-cli-management
CaptainCrouton89
Deploy, manage services, view logs, and configure Railway infrastructure. Use when deploying to Railway, managing environment variables, viewing deployment logs, scaling services, or managing volumes.
azure-devops-rest-api
Tiberriver256
Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the vsts-rest-api-specs repository.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.