How do I install the Erigon Exec From 0 skill?

Run npx skillmds@latest add erigontech/erigon-exec-from-0 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Erigon Exec From 0 safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Erigon Exec From 0?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Erigon Exec From 0 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Erigon Exec From 0?

erigontech (@erigontech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Erigon Exec From 0 by erigontech — Agent Skill

Name: Erigon Exec From 0
Author: erigontech

Erigon Exec From 0

Re-execute all Ethereum blocks from block 0 to reproduce bugs, validate state, or test correctness after code changes. Use this skill whenever the user wants to re-run execution from scratch, reset execution stage, reproduce a state mismatch, validate a fix by re-exec, or run blocks from the beginning on a specific chain/datadir.

erigontech 08fa925 2.0 KB Updated Sep 17, 2026

File contents

Re-execute all blocks from 0

Use this workflow to wipe execution state and re-run all blocks from block 0. Common reasons: reproducing a state root mismatch, validating a bug fix, testing new execution logic end-to-end.

Prerequisites

You need:

--datadir — path to the Erigon data directory (block snapshots must be present)
--chain — chain name (e.g. chiado, mainnet, gnosis, sepolia)

Step 1: Remove state snapshots (keep block snapshots)

go run ./cmd/erigon snapshots rm-all-state-snapshots --datadir <datadir>

This removes .kv state snapshot files but leaves .seg block snapshot files intact, so you don't need to re-download block data.

Step 2: Reset the execution stage

go run ./cmd/integration stage_exec --datadir <datadir> --chain=<chain> --reset

This clears the execution-stage progress in the database so the next run starts from block 0.

Step 3: Run execution

go run ./cmd/integration stage_exec --datadir <datadir> --chain=<chain> --batchSize=8m

Adjust --batchSize to control how frequently state is flushed to disk. Larger = faster but more RAM; 8m is a reasonable default.

Useful optional flags

Profiling (add when you want pprof):

--pprof --pprof.port=6160

Correctness assertions (add when hunting state bugs — slows execution):

ERIGON_ASSERT=true

Stop at a specific block (useful to reproduce a bug at block N):

--block=<N>

Verifying snapshot integrity

If you suspect corrupted snapshot files before running:

go run ./cmd/erigon seg integrity --datadir <datadir> --sample=0.001

---name: erigon-exec-from-0description: Re-execute all Ethereum blocks from block 0 to reproduce bugs, validate state, or test correctness after code changes. Use this skill whenever the user wants to re-run execution from scratch, reset execution stage, reproduce a state mismatch, validate a fix by re-exec, or run blocks from the beginning on a specific chain/datadir.---# Re-execute all blocks from 0Use this workflow to wipe execution state and re-run all blocks from block 0.Common reasons: reproducing a state root mismatch, validating a bug fix, testingnew execution logic end-to-end.## PrerequisitesYou need:- `--datadir` — path to the Erigon data directory (block snapshots must be present)- `--chain` — chain name (e.g. `chiado`, `mainnet`, `gnosis`, `sepolia`)## Step 1: Remove state snapshots (keep block snapshots)```bashgo run ./cmd/erigon snapshots rm-all-state-snapshots --datadir <datadir>```This removes `.kv` state snapshot files but leaves `.seg` block snapshot files intact,so you don't need to re-download block data.## Step 2: Reset the execution stage```bashgo run ./cmd/integration stage_exec --datadir <datadir> --chain=<chain> --reset```This clears the execution-stage progress in the database so the next run starts from block 0.## Step 3: Run execution```bashgo run ./cmd/integration stage_exec --datadir <datadir> --chain=<chain> --batchSize=8m```Adjust `--batchSize` to control how frequently state is flushed to disk. Larger = fasterbut more RAM; `8m` is a reasonable default.## Useful optional flags**Profiling** (add when you want pprof):```--pprof --pprof.port=6160```**Correctness assertions** (add when hunting state bugs — slows execution):```ERIGON_ASSERT=true```**Stop at a specific block** (useful to reproduce a bug at block N):```--block=<N>```## Verifying snapshot integrityIf you suspect corrupted snapshot files before running:```bashgo run ./cmd/erigon seg integrity --datadir <datadir> --sample=0.001```

Frequently asked questions