ethereum/go-ethereum

Geth should handle genesis block with default syncmode

Open

#28,222 opened on Sep 28, 2023

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Go (21,913 forks)batch import
help wantedtype:bug

Repository metrics

Stars
 (51,042 stars)
PR merge metrics
 (Avg merge 21d 10h) (82 merged PRs in 30d)

Description

System information

Geth version: v1.13.2

Expected behaviour

When running without specifying --syncmode=full (i.e. the default i.e. snap sync) geth should transition to full sync automatically for pre-genesis / genesis blocks.

Actual behaviour

Geth doesn't import the 1st block:

Ignoring payload while snap syncing number=1

Steps to reproduce the behaviour

Run geth without --syncmode=full on a new network

Contributor guide

Research direction
Investigate how Geth selects sync mode when no syncmode is provided. Trace the logic in eth/downloader or eth/sync where snap sync is started and where the first block (genesis) is processed. Check conditions that cause 'Ignoring payload while snap syncing' and why full sync isn't triggered automatically for pre genesis blocks.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoEthereum node fundamentals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65