evolve-debugger

Record and replay blockchain execution traces for time-travel debugging.

4|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/evstack/ev-rs --skill evolve-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve-debugger
Source: https://github.com/evstack/ev-rs/tree/main/.claude/skills/evolve-debugger
Command: npx skills add https://github.com/evstack/ev-rs --skill evolve-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers debug complex blockchain application logic by providing tools for tracing execution, replaying transactions, and inspecting state changes over time.

Core Features & Use Cases

  • Trace Recording: Capture detailed execution logs of blockchain transactions and blocks.
  • Time-Travel Debugging: Step backward through execution to pinpoint the exact cause of errors.
  • State Inspection: Query the state of the blockchain at any point in its history.
  • Use Case: When a smart contract test fails unexpectedly, use this Skill to record the execution trace, load it into the debugger, and step back through the transaction to understand precisely where and why the state became invalid.

Quick Start

Use the evolve-debugger skill to load the trace file 'debug_trace.bin' and set a breakpoint on any transaction error.

Frequently Asked Questions about evolve-debugger

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

FAQPage Schema
How do I debug a failing smart contract test and inspect state changes?

To debug a failing smart contract test, record the execution trace, load it into the debugger, and step backward through the transaction to pinpoint exactly where the state became invalid.

Can I replay blockchain transactions and step backward through execution?

Yes, time-travel debugging allows you to replay blockchain transactions and step backward through execution, enabling detailed inspection of state transitions to identify the root cause of errors.

What is the best way to trace execution flow in a deterministic state engine?

The best way to trace execution flow in a deterministic state engine is using breakpoint-driven debugging and state snapshotting to capture detailed logs of transactions and blocks for replay.

Does this debugging tool support manual trace building for Ethereum state analysis?

Yes, the tool supports manual trace building for Ethereum state analysis, allowing you to query the blockchain state at any point in its history and inspect state changes over time.

How do I set a breakpoint on a transaction error using a trace file?

To set a breakpoint on a transaction error, load the recorded trace file into the debugger and apply breakpoints to isolate and analyze the specific execution flow where the failure occurred.