lidofinance / lidofinance/validator-ejector
Syncing consensus state can suppress exit requests past the cache cursor
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 19
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 7
Description
Locations
validator-ejector/src/services/consensus-api/service.ts:31-34validator-ejector/src/services/consensus-api/service.ts:61-73
Summary
Startup permits exit processing while the selected consensus endpoint is still syncing, and it does not check the readiness of backup endpoints. Stale consensus state can therefore cause an execution-layer exit event to be discarded permanently for the running process.
Root cause
syncing()performs a first-success fallback request and returns onlydata.is_syncing.checkSync()merely logs a warning when that value is true instead of rejecting startup.- Consequently, a syncing primary is accepted and a syncing backup is never checked if the primary initially succeeds.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start in validator-ejector/src/services/consensus-api/service.ts at lines 31-34 and 61-73, then trace how syncing() and checkSync() are used during startup. The change is done when syncing primary and backup consensus endpoints cannot allow exit processing to start, and the behavior is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100