lambdaclass / lambdaclass/lambda_ethereum_consensus
Use a secure channel for serving the validator API
Open
Nobody has claimed this yet.
Validator API
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
As per the spec: https://ethereum.github.io/keymanager-APIs/
All routes SHOULD be exposed through a secure channel, such as with HTTPs, an SSH tunnel, a VPN, etc.
All sensitive routes MUST be authenticated with a token.
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 the validator API entry points and checking how routes are currently exposed and authenticated. Compare the existing behavior with the linked keymanager API specification. Done means all routes use a secure channel and sensitive routes require token authentication, with coverage for the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100