lambdaclass / lambdaclass/lambda_ethereum_consensus
Support kdf paths on Keystore
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Context: #1013
ERC-2335 keystores have a path field with a EIP-2333 path for deriving the secret. We should support non-empty values of that field.
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
Read context issue #1013 and the ERC-2335 and EIP-2333 references, then locate the Keystore implementation and its existing handling of the path field. Done means non-empty EIP-2333 paths are supported for deriving the secret while existing empty-path behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100