lambdaclass / lambdaclass/lambda_ethereum_consensus
Unify listen address and discovery address formats in `Libp2pPort`
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Currently listen_addresses expects a Multiaddr, while discovery_address expects a host:port pair.
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 locating Libp2pPort and tracing how listen_addresses and discovery_address are parsed. Check existing tests or callers for the accepted address forms, then clarify which common format is intended and add coverage showing both fields follow it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100