lambdaclass / lambdaclass/lambda_ethereum_consensus
Signing and withdrawal credential storage
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We need to store validator credentials:
- Signing key pair: BLS public key + privkey.
- Withdrawal credentials. 32 byte, where the first is a prefix and the rest is a payload. Two options:
- BLS:
BLS_WITHDRAWAL_PREFIX ++ hash(bls_withdrawal_pubkey). No privkey recquired. - ETH1:
ETH_ADDRESS_WITHDRAWAL_PREFIX ++ "\x00" * 11 ++ eth1_withdrawal_address.
- BLS:
Note: In eth1 deposit messages there should be credentials being sent to the consensus layer, but this is to set the validator that this node is running. Potentially we could store multiple validators keys, but let's start supporting one.
Spec ref: link
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 with the validator initialization section in the linked validator specification and inspect the repository's validator initialization entry point. Define storage for one validator's BLS signing key pair and either BLS or ETH1 withdrawal credentials; done means both credential forms are represented according to the stated 32-byte layouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- blockchain, cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100