lambdaclass / lambdaclass/lambda_ethereum_consensus
Implement node version endpoint
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
When an external validator tries to connect to our node it fails to see it as active because node/version is not implemented. We should do it, at least with a hardcoded version.
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
Locate the existing node endpoint handlers and their tests, then inspect how requests to node/version are routed. Implement the endpoint with the requested version response, including the hardcoded version if no dynamic source is identified, and verify that an external validator can recognize the node as active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100