Menu
Reference for manipulating Erigon datadirs. Use this when the user wants to perform operations on Erigon data directories.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build pristine State Actor datadirs and run repeatable benchmarkoor performance benchmarks against a locally built Erigon image using protected native Linux OverlayFS. Use for first-time benchmarkoor setup, Glamsterdam compute or stateful repricing suites, local client image overrides, pristine-state protection, result extraction, before/after MGas/s comparisons, and cross-client ranking tables.
Run Erigon CI checks locally and/or trigger them remotely on a branch via GitHub Actions workflow_dispatch. Use this when you need to verify a branch passes all CI before or after pushing — especially for branches like bal-devnet-2 that don't auto-trigger on push/PR events.
Implement a new EIP for a hardfork under development in Erigon. Use when the user asks to implement, port, or wire up an EIP — covers spec lookup, dep analysis, prior-work check, implementation, lint, tests, and a wrap-up saved to `agentspecs/`.
Run the full Erigon test suite locally using GOGC=80 make test-all. Use this before marking a PR ready for review. Equivalent to the "All tests" CI workflow.
Run Erigon tests with Go race detector to find data races and concurrency bugs. Use this for concurrency-sensitive changes (parallel executor, p2p, txpool). Takes 30-60 minutes.
Run Erigon Hive simulator tests locally or via GitHub Actions. Tests EL/CL protocol interoperability (engine API, RPC compat, EEST fixtures). Requires Docker and either `act` (for CI simulation) or direct hive invocation.
| name | erigon-datadir |
| user-invocable | false |
| description | Reference for manipulating Erigon datadirs. Use this when the user wants to perform operations on Erigon data directories. |
| allowed-tools | Bash, Read, Glob |
Given a source path and destination path, follow this procedure exactly.
All checks must pass before copying. Abort on the first failure.
test -d <src> — abort if missing<src>/nodekey (file)<src>/snapshots/ (directory)<src>/chaindata/ (directory)test ! -e <dst> — abort if it already existstest -w "$(dirname <dst>)" — abort if notdu -sh <src> and always tell the user the size before proceedingmount output. If the mount entry contains apfs, use the APFS CoW procedure below; otherwise use the full-copy procedure.Use this when the destination is on an APFS volume.
cp -ac <src> <dst> — this creates a CoW clone that is near-instant and consumes no extra disk space.rm -rf <dst>/chaindataUse this when the destination is NOT on APFS.
df -h "$(dirname <dst>)" and compare available space to the source size. If available space is less than source size, abort and tell the user — do not proceed.cp -a <src> <dst> to recursively copy the entire datadir. This is a long-running operation for large datadirs — run in background.After either procedure completes, confirm success by listing the destination contents and comparing against the source (minus chaindata/ for APFS copies).