As per the help command

--test-drop-download : For net tests: in download, discard ALL blocks instead checking/saving them (very fast)

 

--fast-block-sync arg (=1) : Sync up most of the way by using embedded, known block hashes.

What is the difference between these two modes of syncing?

As per the help command

--test-drop-download : For net tests: in download, discard ALL blocks instead checking/saving them (very fast)

--fast-block-sync arg (=1) : Sync up most of the way by using embedded, known block hashes.

What is the difference between these two modes of syncing?

As per help command

--test-drop-download : For net tests: in download, discard ALL blocks instead checking/saving them (very fast)

--fast-block-sync arg (=1) : Sync up most of the way by using embedded, known block hashes.

What is the difference in these 2 modes of syncing?

As per the help command

--test-drop-download : For net tests: in download, discard ALL blocks instead checking/saving them (very fast)

--fast-block-sync arg (=1) : Sync up most of the way by using embedded, known block hashes.

What is the difference between these two modes of syncing?