I'm syncing my geth client with ropsten testnet and just realized how slow is the syncing process after a certain block(trying to retrieve information from blocks that got in blockchain yesterday) for a couple of hours.
Basically I got several messages like this one, saying a potential rewrite attack:
I0111 08:28:09.783928 eth/downloader/downloader.go:723] Peer 7335842dc6658f60 [hs 0.00/s, bs 0.00/s, rs 0.00/s, ss 0.00/s, miss 0, rtt 13.155759485s]: potential rewrite attack: #224778 [00000000�] <= #224778 limit
My question differs from this question as I'm not yet synced as I've checked out. One of the answers there doesn't apply here as I made sure I referenced the ropsten genesis block and checked the hash of that genesis block in my local database to certify I'm running to get in sync with the right network. So, I don't believe the cause of this high delay in my node syncing process isn't actually the addition of old morden to my local database.
Is this behavior expected when syncing? Is there any way to maximize the peer coverage to speed up the whole process if comes to that?
Best Answer
You can use
--fastflag.The fast flag enables fast syncing through state downloads rather than downloading the full block data.Another flag that can be used along with
--fastto sync your client more quickly is--cache. The Cache flag can be used to change the default alloted memory for a fast sync.Refer this :- https://medium.com/@crissimrobert/a-guide-to-ropsten-testnet-setup-f8952d615417