lambdaclass / lambdaclass/lambda_ethereum_consensus
Format peer ID manually in /node/identity endpoint
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we format the peer ID in the Go side and pass it as pretty_peer_id in the GetNodeIdentity proto message, but it can be derived from the raw peer_id.
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 at the /node/identity endpoint and the GetNodeIdentity proto message; trace how raw peer_id and pretty_peer_id are handled on the Go side. Done means the endpoint derives the formatted peer ID from raw peer_id instead of receiving pretty_peer_id.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, go
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100