ChainSafe / ChainSafe/lodestar-prover

Verification of `eth_getBlockNumber` for prover should not forward request

Open
#7 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

### Describe the bug

Currently we documented that `eth_blockNumber` will be forwarded to EL. This may cause to return the wrong block number which is not synced with the light client.

### Expected behavior

Return the latest block number signed by the current sync-committee.

### Steps to reproduce

_No response_

### Additional context

_No response_

### Operating system

Linux

### Lodestar version or commit hash

1.9.x

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by tracing how the prover handles eth_blockNumber and eth_getBlockNumber, then identify where the response is forwarded to the execution layer. Done means the returned value is the latest block number signed by the current sync committee rather than an unsynchronized execution-layer value.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend-api-design, blockchain
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.