lambdaclass / lambdaclass/ethlambda
Cache fork-choice weights in `LiveChain`
Nobody has claimed this yet.
- #235 by @pablodeymo — closed without merging
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Description
We currently discard computed weights after each head update. We should instead cache them in our LiveChain and update it only with new attestations.
For reference, Lighthouse uses a "proto-array" implementation: https://github.com/sigp/lighthouse/tree/stable/consensus/proto_array/src
while Prysm uses a doubly-linked tree: https://github.com/OffchainLabs/prysm/tree/develop/beacon-chain/forkchoice/doubly-linked-tree
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 LiveChain implementation and its head-update path, then review the referenced Lighthouse proto-array and Prysm doubly-linked-tree designs. Done means computed fork-choice weights persist in LiveChain and are updated only when new attestations arrive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100