smartcontractkit / smartcontractkit/chainlink
[FEAT] Fail over eth1 when primary is not synced
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
Improve the eth1 failover mechanic so that failover occurs when primary eth1 is reachable, but not synced to head
Motivation
Primary eth1 may not fail entirely, and instead just fail to keep up with head
Contributor 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.
Research direction
No files, tests, or entry points are named. Locate the eth1 failover mechanism and the logic that determines whether the primary is synced to head; done means failover occurs when the primary remains reachable but falls behind, with coverage for that condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100