nspcc-dev/neo-go

Test `NeoFSStateSyncExtensions` on large chains

Open

#3,907 opened on May 20, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (108 forks)auto 404
I4S2U3blockedgood first issuetask

Repository metrics

Stars
 (132 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe.

NeoFSStateSyncExtensions are tested only on private network with low number of blocks (~200K).

Describe the solution you'd like

Test NeoFSStateSyncExtensions on FS chains at 15M+ blocks and on N3 chains as far. Ensure state synchronisation works as expected in different scenarios: interruption in the middle of headers/blocks/MPT sync/statejump, problems with connection to NeoFS storage etc. Ensure state compatibility and node's DB completeness.

Describe alternatives you've considered

Leave it to @532910.

Additional context

Depends on #3898, #3825 and we don't yet have state data uploaded to NeoFS mainnet, so need to run uploaders firstly.

Contributor guide

Research direction
Set up NeoFS uploaders to upload state data for large chains (15M+ blocks), then implement integration tests for NeoFSStateSyncExtensions covering interruptions and connection issues.
Tech stack
go
Domain
backendblockchain
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoNeoFSNeo blockchain
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20