القائمة
Integration test plan for erigondb.toml settings resolution across 3 runtime scenarios (legacy, fresh+downloader, fresh+no-downloader)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run Ethereum Hive integration tests against a local Erigon build, including engine, RPC compatibility, standard EEST, BAL/Amsterdam EEST, and RLP suites. Use when setting up an ephemeral Hive environment, selecting or running Hive suites, interpreting Hive failures, or cleaning up Hive test resources.
Autonomous Goal-directed Iteration. Apply Karpathy's autoresearch principles to ANY task. Loops autonomously — modify, verify, keep/discard, repeat. Supports optional loop count via Claude Code's /loop command.
Use the 'erigon seg step-rebase' command to change the step size of an existing datadir. Use when the user wants to rebase segments or modify step sizes.
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 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.
| name | erigondb-sync-integration-test-plan |
| description | Integration test plan for erigondb.toml settings resolution across 3 runtime scenarios (legacy, fresh+downloader, fresh+no-downloader) |
| allowed-tools | Bash, Read |
| user-invocable | false |
Verify that erigondb.toml settings are correctly resolved across three distinct runtime scenarios: legacy datadirs, fresh sync with downloader, and fresh sync without downloader.
Use this plan after any changes to the erigondb.toml resolution logic (creation, defaults, legacy detection, downloader delivery) to confirm all paths still work.
Two values must be provided by the caller:
| Parameter | Description | Example |
|---|---|---|
| chain | Chain name passed to --chain= | hoodi, mainnet |
| legacy datadir | Path to an existing Erigon datadir that has preverified.toml but no erigondb.toml | ~/eth-nodes/erigon33-hoodi-stable |
All scenarios use --prune.mode=archive.
/erigon-build if ./build/bin/erigon does not exist.snapshots/preverified.toml and must not contain snapshots/erigondb.toml./erigon-network-ports for reference. Each scenario uses a different port offset (+100, +200, +300) via /erigon-ephemeral conflict detection.Goal: Starting on a legacy datadir (has preverified.toml, no erigondb.toml) creates erigondb.toml with legacy settings (step_size = 1562500).
/erigon-ephemeral (Mode B: clone). This gives an isolated copy so the original is untouched.snapshots/preverified.toml existssnapshots/erigondb.toml does not exist/erigon-ephemeral port conflict detection):
./build/bin/erigon \
--datadir=<clone-path> \
--chain=<chain> \
--prune.mode=archive \
<port flags at +100 offset>
Creating erigondb.toml with LEGACY settings).cat <clone-path>/snapshots/erigondb.toml
step_size = 1562500 and references_in_commitment_branches = trueGoal: A fresh datadir (no preverified.toml, no erigondb.toml) starts with code defaults (step_size = 1562500), then the downloader delivers the network's erigondb.toml during the header-chain phase, which may have different settings (e.g., step_size = 390625 for hoodi).
/erigon-ephemeral (Mode A: empty)../build/bin/erigon \
--datadir=<empty-path> \
--chain=<chain> \
--prune.mode=archive \
<port flags at +200 offset>
erigondb.toml not found, using defaults) with step_size=1562500.[1/6 OtterSync] Downloader completed header-chainReading DB settings from existing erigondb.tomlerigondb stepSize changed, propagating (if the network's settings differ from the code defaults)cat <empty-path>/snapshots/erigondb.toml
erigondb.toml (check the chain's webseed for the canonical values).--no-downloaderGoal: A fresh datadir with --no-downloader immediately writes erigondb.toml with code defaults (step_size = 1562500).
/erigon-ephemeral (Mode A: empty).--no-downloader:
./build/bin/erigon \
--datadir=<empty-path> \
--chain=<chain> \
--prune.mode=archive \
--no-downloader \
<port flags at +300 offset>
Initializing erigondb.toml with DEFAULT settings) with step_size=1562500.cat <empty-path>/snapshots/erigondb.toml
step_size = 1562500 and references_in_commitment_branches = true (code defaults, since no downloader to provide network settings)| Scenario | Condition | Expected step_size | Expected references_in_commitment_branches | File timing |
|---|---|---|---|---|
| A (legacy) | Creating erigondb.toml with LEGACY settings log | 1,562,500 | true (written explicitly) | Written immediately on startup |
| B (fresh+downloader) | erigondb.toml not found, using defaults then erigondb stepSize changed, propagating | Code default 1,562,500 then network value (chain-dependent) | Resolves to true in memory until the downloader delivers the file; whatever the network publishes thereafter (a producer-published plain snapshot set ships false) | After downloader delivers it |
| C (fresh+no-downloader) | Initializing erigondb.toml with DEFAULT settings (nodownloader) log | 1,562,500 | true (written explicitly) | Written immediately on startup |
The references_in_commitment_branches field governs whether new commitment merges write referenced (short-key) .kv files. It resolves identically to step_size across the three scenarios — absent field normalizes to true in memory, and a downloaded erigondb.toml is never rewritten (it is synced snapshot metadata, so a producer's published false survives). The resolution logic is unit-tested in db/state/erigondb_settings_test.go (TestResolveErigonDBSettings*); these runtime scenarios confirm the same behavior end-to-end.
references_in_commitment_branches = true.true. After delivery the field reflects the network's published value (a plain-snapshot producer ships false).references_in_commitment_branches = true.references_in_commitment_branches governs only new commitment merges; reads are version-aware and stay correct regardless of the flag (a v2.0 commitment .kv whose range ≥ threshold is referenced/short-key; a v2.1 file is plain). To publish a snapshot set whose commitment files carry no plain-key references:
snapshots/erigondb.toml, set references_in_commitment_branches = false before running merges.v2.2 .kv files. Existing v2.1 referenced files convert to plain lazily as they are merged — no upfront migration.erigondb.toml with the snapshot set. Consumers read the file and inherit false; a downloaded erigondb.toml is never rewritten, so the producer's false survives.This supersedes the build-time const flip (awskii/36exp): no binary divergence and no CLI flag. Default nodes (field absent → true) keep writing byte-compatible v2.1 referenced files with no behavior change.
After all scenarios complete, ensure all ephemeral datadirs and processes are cleaned up. Use /erigon-ephemeral Step 5 (cleanup) for each instance, or Step 6 (leftover detection) to find any stragglers.