db/state: a standalone index missing its first file starts past 0, and range reads below it return nothing

Open
#26,418 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@AskAlexSharov is already working on this.

Since Nov 17, 2026.

Assessment

This issue has not been assessed yet.

Description

A standalone index (logaddrs, logtopics, tracesfrom, tracesto) missing its first .ef file is not in the dirty inventory, so its visible list starts at the next file and nothing checks that it starts at 0.

Failing case: logaddrs.0-X.ef is deleted or never downloaded, later files are intact.

  • the visible list covers [X, end) and its end passes the files/DB gap check
  • IdxRange below X finds no file, and recentIterateRange returns empty because the range ends below files.EndTxNum()
  • eth_getLogs over [0, X) returns no logs, with no error

Same class as #26358 (values lists). Same on main and with #25965.

Dominant language
Go
Stars
3.6k
Forks
1.6k
Avg merge
1d 17h
Merged PRs (30d)
820

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from erigontech/erigon

All issues in erigontech/erigon

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.