Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cache fork-choice weights in `LiveChain`

Open
#167 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #235 by @pablodeymo — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
blockchain

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.

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

Dominant language
Rust
Stars
82
Forks
28
Avg merge
1d 20h
Merged PRs (30d)
20

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambdaclass/ethlambda

All issues in lambdaclass/ethlambda

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.