-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Ropsten bootnodes use wrong fork #8845
Comments
Parity Bootnode is on the right side of the fork (can be checked here: https://ropsten-stats.parity.io/) but it seems that you were not able to warp sync with it. Checking why now. To make sure to warp-sync on the right one, you can specify our bootnode enode in a Using the bootnode: An alternative is to sync with |
I tried to drop db and sync again and today it was successful. I guess it was related the recent consensus issue. Probably it make sense to add some mechanism to avoid synchronization with old clients. Also in this situation I could edit network.json and leave only geth nodes and latest parity nodes. |
Hi,
|
@usmananwar to sync the right chain, please do the following:
|
actual
Running with option --warp-barrier 3000000
Last block is 3380734
expected behavior
Block number should grow every minute
steps to reproduce
Stop parity
Remove database folder
Run parity
Wait to be synced
The text was updated successfully, but these errors were encountered: