I was syncing ropsten testnet using geth. Command used-
geth --testnet --syncmode "full"
At some time, eth.syncing
returned-
{
currentBlock: 353883,
highestBlock: 1172714,
knownStates: 0,
pulledStates: 0,
startingBlock: 353878
}
Notice the highest block. Its supposed to be 24xxxxx.
When I let it sync, syncing stopped at 1172xxx block.
I checked blocks manually and compared them with http://ropsten.etherscan.io/ , blocks were same as ethscan upto 585000 blockNumber(and different afterwards), that is the block number where ropsten testnet revival took place from.
Now I assume that it somehow synced with a fork where revival did not take place.
- Can anybody explain me how did it happen? Aren't all nodes on same fork?
- How can I make sure when I start geth that it doesn't sync with blockchain from pre-ropsten revival fork?
- Can something like this happen on main-net?