lambdaclass / lambdaclass/lambda_ethereum_consensus
CLI for validator initialization with credentials
Open
Nobody has claimed this yet.
validator
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
At the bare minimum, there should be an option to start the node with a credential path, which is parsed, and then saved it in the credential storage, to let the node know that it's running in the name of a specific validator and it should perform its duties when the slot/epoch/sync committee period requires so.
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
The issue does not name files or tests. Start by tracing CLI startup and the existing credential-storage path, then determine how validator duties are initialized. Done means a credential path can be accepted, parsed, stored, and used to associate the node with the validator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100