skills.rest
lodekeeper
lodekeeperCOMMUNITY
Explore all skills by this author →
GitHub

local-mainnet-debug

Run a local Lodestar beacon node against mainnet peers with checkpoint sync and engineMock.

4|1|Updated Feb 20, 2026
Search Tags:#debugging#networking#peer discovery#mainnet#lodestar#beacon node
One-click install
npx skills add https://github.com/lodekeeper/dotfiles --skill local-mainnet-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-mainnet-debug
Source: https://github.com/lodekeeper/dotfiles/tree/main/skills/local-mainnet-debug
Command: npx skills add https://github.com/lodekeeper/dotfiles --skill local-mainnet-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps developers debug complex networking and peer discovery issues in the Lodestar beacon node by running a local instance connected to the mainnet.

Core Features & Use Cases

  • Local Mainnet Simulation: Run a beacon node against real mainnet peers without needing a full execution client.
  • Deep Protocol Debugging: Utilize verbose logging, metrics, and optional instrumentation to pinpoint issues.
  • Use Case: Investigate why your Lodestar node is failing to discover peers or experiencing intermittent connection drops by running this skill and analyzing the detailed logs and metrics.

Quick Start

Execute the provided bash command to start a local mainnet debug instance of the Lodestar beacon node.

Frequently Asked Questions about local-mainnet-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Lodestar beacon node peer discovery issues against mainnet?▼

Debug Lodestar peer discovery issues by running a local beacon node instance connected to mainnet peers using checkpoint sync and engineMock. This simulates a realistic network environment to analyze intermittent connection drops via detailed logs and metrics.

Can I run a Lodestar beacon node against mainnet without a full execution client?▼

You can run a Lodestar beacon node against mainnet without a full execution client by utilizing the engineMock feature. This enables local mainnet simulation for deep protocol debugging while bypassing the need for heavy execution layer dependencies.

How does checkpoint sync help with local mainnet debugging in Lodestar?▼

Checkpoint sync enables rapid initialization of a local Lodestar beacon node by fetching a recent mainnet state. This allows immediate connection to mainnet peers for debugging networking and protocol failures without waiting for a full sync.

What's the best way to troubleshoot Lodestar networking and protocol failures locally?▼

Troubleshoot Lodestar networking failures by executing specific command-line flags to configure verbose logging and instrumentation. Running the local mainnet instance generates detailed metrics and logs to pinpoint peer discovery and protocol issues.

Do I need specific command-line flags to configure Lodestar for local mainnet debugging?▼

Specific command-line flags are required to configure logging, checkpoint sync, and engineMock for local mainnet debugging. These flags activate the verbose output and network simulation needed to investigate peer discovery and connection issues.

Related Skills

Explore More Software Engineering Skills→
lodekeeperlodekeeper
4

join-devnet

Join Ethereum devnets with a local Lodestar beacon node using engineMock.

Community
Intermediate
ClipboardHealthClipboardHealth
66

datadog-investigate

Query Datadog logs, metrics, and traces to diagnose system failures.

Official
Advanced
lodekeeperlodekeeper
4

release-metrics

Compare beta and stable release metrics using Grafana and Prometheus data.

Community
Advanced
lodekeeperlodekeeper
4

grafana-loki

Query Grafana Loki logs for Lodestar beacon nodes, execution clients, and validators.

Community
Intermediate