notifications: publish finality-only fork-choice updates
Maintainers usually reply within 1 day
@yperbasis is already working on this.
Since Nov 18, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- backend, distributed-systems
Research direction
Read execution/execmodule/forkchoice.go and the notification contract in #26013, then trace the short-circuit path and publisher behavior for same-head fork-choice updates. Check the subscription reset and publication-sequence logic added in #25515. Done means changed finality metadata reaches existing subscribers and reset reads racing a finality-only commit see the committed marker, without replaying headers or logs or forcing full state recovery; unchanged markers remain a no-op.
Written by the indexing model from the issue text.
Description
A successful same-head fork-choice update that changes only safe/finalized markers commits those markers without publishing a state-change batch. Existing subscribers keep the old finality until a later block; a subscriber whose reset read races that commit can also start with the old marker.
In execution/execmodule/forkchoice.go, the short-circuit path dispatches only when the accumulator has pending changes. With head 4, finalized 1, and an empty accumulator, updating finalized to 3 commits the marker but never calls the publisher. The state version remains unchanged, so the subscription publication-sequence check added in #25515 cannot detect this commit.
The observed consequence is delayed pruning of the txpool's mined-blob cache. Publish changed head metadata independently of execution-state deltas, without replaying headers/logs or forcing full state recovery. Cover an existing subscription and a reset read racing a finality-only commit, including the no-op case where no markers changed. Coordinate the notification contract with #26013.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.6k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 820
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from erigontech/erigon
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
flaky test
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
erigontech/erigon#26230 ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: pending nonce counts past gaps in the poolPossibly taken @yperbasis claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
erigontech/erigon#26014 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
tracing: expose custom error selector and raw payload in callTracer revertReasonPossibly taken @lupin012 claimed this 9 days ago. OpenRPC
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
erigontech/erigon#25928 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: remove redundant blob/commitment length checkPossibly taken @yperbasis claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
erigontech/erigon#25432 ·
Maintainers usually reply within 1 day
All issues in erigontech/erigon
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day