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

join-devnet

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to quickly connect a local Lodestar beacon node to an existing Ethereum devnet without needing to run a full execution client, simplifying testing and debugging.

Core Features & Use Cases

  • Devnet Connection: Easily join public or custom Ethereum devnets (e.g., ethpandaops).
  • Engine Mock: Operates using an engine mock, eliminating the need for an execution client.
  • Use Case: Debugging sync issues, testing new beacon chain features, or monitoring devnet activity by running a local beacon node connected to a live devnet.

Quick Start

Run a local Lodestar beacon node to join the epbs-devnet-0 devnet using engineMock.

Frequently Asked Questions about join-devnet

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

FAQPage Schema
How do I join an Ethereum devnet without running an execution client?▼

You can join an Ethereum devnet without an execution client by running a local Lodestar beacon node configured with an engine mock. This eliminates the need for a full execution layer while still allowing you to connect to live devnets.

Can I use Lodestar to debug beacon node sync issues on a devnet?▼

Yes, you can use a local Lodestar beacon node to debug sync issues on an Ethereum devnet. By operating with an engine mock, it isolates the beacon layer to simplify testing and monitoring of devnet activity.

What is an engine mock and when do I need it for Ethereum devnet testing?▼

An engine mock simulates the execution client in Ethereum devnet testing. You need it when you want to run a local Lodestar beacon node to monitor or debug devnet activity without the overhead of deploying a full execution client.

Does connecting to a custom Ethereum devnet require manual chain configuration downloads?▼

Connecting to a custom Ethereum devnet does not require manual chain configuration downloads. The setup automatically downloads necessary artifacts like chain configurations and genesis states to facilitate instant connection.

What are the limitations of using an engine mock for beacon node testing?▼

Using an engine mock for beacon node testing limits your environment to beacon layer activity only. Because it bypasses the actual execution client, you cannot test complex transaction execution or smart contract interactions on the devnet.

Related Skills

Explore More Software Engineering Skills→
lodekeeperlodekeeper
4

local-mainnet-debug

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

Community
Advanced
YukiIto1999YukiIto1999

hunting-for-cobalt-strike-beacons

Detect Cobalt Strike beacon activity in Zeek logs using TLS fingerprints and timing analysis.

Community
Advanced
lodekeeperlodekeeper
4

grafana-loki

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

Community
Intermediate
IstoraMandiriIstoraMandiri

hive-run

Orchestrate Hive integration tests for Ethereum clients via CLI.

Community
Intermediate