You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SnapSync is ready for prime-time. We are also preparing to ship snap server, the final piece of the puzzle.
This ticket tracks some final cleanup for UX and simplicity as we move Snap to non-experimental and the default for the client over time.
Since SNAP is an extension of FAST in the codebase, the log entries for a SNAP sync node all show as FAST sync e.g. "main | INFO | FastSyncDownloader | Starting sync". It's not ideal when looking through logs that the class names logged out can mislead you as to which sync mode is being used. We should tidy this up. SnapSyncDownloader logging as FastSyncDownloader #6386
SNAP sync and --fast-sync-min-peers. In a PoW or PoA network this flag applies to SNAP and CHECKPOINT sync. A synonym should be added as part of moving it out of experimental, with --fast-sync-min-peers deprecated for removal in a future version. We could use --sync-min-peers and update the docs to reflect this flag only impacts non-PoS networks in Besu. Alias --fast-sync-min-peers to --sync-min-peers #6327
SnapSync is ready for prime-time. We are also preparing to ship snap server, the final piece of the puzzle.
This ticket tracks some final cleanup for UX and simplicity as we move Snap to non-experimental and the default for the client over time.