devnet-debug

Debug Kurtosis-based Ethereum devnets by tracing logs and applying fixes until blocks advance.

98|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/jiayaoqijia/eth2030 --skill devnet-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devnet-debug
Source: https://github.com/jiayaoqijia/eth2030/tree/main/.claude/skills/devnet-debug
Command: npx skills add https://github.com/jiayaoqijia/eth2030 --skill devnet-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug a Kurtosis devnet that is not producing blocks. Iterates through logs → code correlation → fix → rebuild → retest until the chain advances.

Core Features & Use Cases

  • Detect stalled devnets and classify failure modes (engine/API, RPC, or consensus) to focus debugging efforts.
  • Provide an end-to-end debug workflow including boot, observation, log inspection, patch iteration, and retesting until blocks progress.
  • Offer practical quick-start steps and example commands to reproduce issues and verify fixes in a Kurtosis devnet context.

Quick Start

Start the Kurtosis devnet, observe boot logs, classify the failure, implement fixes, rebuild images, and retest until the chain advances.

Frequently Asked Questions about devnet-debug

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

FAQPage Schema
Why is my Kurtosis Ethereum devnet not producing blocks?

A stalled Kurtosis devnet typically fails due to engine API, RPC, or consensus issues. You must trace boot logs, correlate failures, apply code fixes, rebuild images, and retest until the Ethereum chain advances.

How do I debug a stalled devnet and trace blockchain failures?

Debugging a stalled devnet requires a structured workflow: start the Kurtosis environment, observe boot logs, classify the failure mode, implement patches, rebuild, and retest iteratively until block progression resumes.

What's the best way to correlate Ethereum devnet logs with code failures?

The best way to correlate devnet logs with failures is iteratively matching log signals to specific code patches, rebuilding your Ethereum images, and retesting to verify that the applied fix resolves the stalled block progression.

Does this devnet debugging workflow work for non-Kurtosis blockchain environments?

No, this devnet debugging workflow is strictly limited to Kurtosis-based Ethereum environments. It relies on Kurtosis-specific boot, observation, log inspection, patch iteration, and retesting cycles to verify success.

How do I classify failure modes in a stalled Ethereum devnet?

To classify failure modes in a stalled Ethereum devnet, inspect the boot logs to determine whether the issue stems from the engine API, RPC endpoints, or consensus layer, then focus your debugging efforts accordingly.

What observable signals verify a Kurtosis devnet fix is successful?

Successful devnet fixes are verified through observable signals including continuous block progression, clean boot logs, and stable node status within the Kurtosis environment after rebuilding and retesting the patched images.