lambdaclass / lambdaclass/lambda_ethereum_consensus
Blob not available mark canonical block as invalid
Open
Nobody has claimed this yet.
bug
P0
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Yesterday, an issue related to blob availability made us mark a canonicla block as invalid which stopped the processing of the canonical chain, here are the logs:
| | 2025-02-06 20:05:37.703 | [PendingBlocks] Saving block as invalid after ForkChoice.on_block/2 error: blob data not available |
| | 2025-02-06 20:05:37.702 | [Fork choice] Failed to add block: blob data not available |
| | 2025-02-06 20:05:37.617 | [Fork choice] Adding new block |
| | 2025-02-06 20:05:36.651 | [Gossip] Block received, block.slot: 6929128. |
| | 2025-02-06 20:05:36.005 | [Libp2p] Slot transition |
| | 2025-02-06 20:05:24.004 | [Libp2p] Slot transition |
| | 2025-02-06 20:05:12.836 | [Fork choice] Recomputed head |
| | 2025-02-06 20:05:12.836 | [Fork choice] Added new block |
| | 2025-02-06 20:05:12.836 | Topic(:block) doesn't have subscribers |
| | 2025-02-06 20:05:12.828 | [Fork choice] Block processed. Recomputing head. |
| | 2025-02-06 20:05:12.620 | [Fork choice] Adding new block |
| | 2025-02-06 20:05:12.291 | [Gossip] Block received, block.slot: 6929126. |
| | 2025-02-06 20:05:12.004 | [Libp2p] Slot transition |
| | 2025-02-06 20:05:00.822 | [Fork choice] Recomputed head |
| | 2025-02-06 20:05:00.822 | [Fork choice] Added new block
logs: d/90EXFQnIk/node?orgId=1&viewPanel=23&from=1738882800000&to=1738883160000&editPanel=23
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
No source files or tests are named. Start by tracing the PendingBlocks and ForkChoice paths referenced in the logs, then investigate how a “blob data not available” error causes a canonical block to be marked invalid. Done means unavailable blob data no longer stops canonical-chain processing, with regression coverage for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100