lambdaclass / lambdaclass/lambda_ethereum_consensus
Use local weak subjectivity checkpoint for "run the node" CI check
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Blocked by #726
We are currently trying a checkpoint sync with a public URL. If that endpoint were to be down, our CI would fail. This is a problem that can be solved by just making the data up ourselves.
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
Start by reading blocked issue #726 and locating the existing checkpoint sync used by the “run the node” CI check. The work is complete when that check creates or uses a local weak subjectivity checkpoint without depending on the public URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100