-
Notifications
You must be signed in to change notification settings - Fork 684
Open
Labels
P:operator-experiencePriority: Improve experience for operatorsPriority: Improve experience for operatorsstate-synctrackingA complex issue broken down into sub-problemsA complex issue broken down into sub-problems
Description
This is a high-level tracking issue for us to keep track of major problem areas in state sync.
- Nodes sending snapshots which contain 0 chunks
- Our team is not totally familiar with the differences between state sync in
v0.36.x
andmain
- We are unsure of what a holistic, good design for state sync currently looks like
Solutions
Let's try to keep our focus on the problem space as far as possible. Ideally recommendations as to solutions should clearly articulate the problem they're trying to solve.
- Write up an RFC reiterating the goals of state sync and summarizing the current problem space
- Backport differences in state sync from
v0.36.x
tomain
- Support State sync verification over p2p #266
- State sync from local snapshot #27
cason
Metadata
Metadata
Assignees
Labels
P:operator-experiencePriority: Improve experience for operatorsPriority: Improve experience for operatorsstate-synctrackingA complex issue broken down into sub-problemsA complex issue broken down into sub-problems