lambdaclass / lambdaclass/lambda_ethereum_consensus
GET /node/* - Implement Node endpoints
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Implement the Node endpoints of the Beacon API, this could become an umbrella task pointing to smaller task for each individual endpoint. for now this is just to track the progress in the Node endpoints implementation:
-
eth/v1/node/identity -
eth/v1/node/peers -
eth/v1/node/peers/{peer_id} -
eth/v1/node/peer_count -
eth/v1/node/version -
eth/v1/node/syncing- semi-stub implementation.
-
eth/v1/node/health- semi-stub implementation
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 with the Beacon API Node specification linked in the issue and compare it with the checked-off identity and version endpoints. Review the remaining checklist entries for peers, individual peers, peer count, syncing, and health, including the noted semi-stub implementations. Done means the remaining Node endpoints are implemented and the checklist accurately reflects their status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100