Geth – Resolving Slow Testnet Sync Issues

go-ethereumropstentestnets

I am trying to deploy a smart contract in the ethereum testnet and in order to accomplish that I tried to sync the Ethereum testnet "ropsten" using geth. I used the command below to do it.

geth --testnet --syncmode "fast" --rpc --rpcapi db,eth,net,web3,personal --
cache=1024  --rpcport 8545 --rpcaddr 127.0.0.1 --rpccorsdomain "*" --
bootnodes "enode://20c9ad97c081d63397d7b685a412227a40e23c8bdc6688c6f37e97cfbc22d2b4d1db1510d8f61e6a8866ad7f0e17c02b14182d37ea7c3c8b9c2683aeb6b733a1@52.169.14.227:30303,enode://6ce05930c72abc632c58e2e4324f7c7ea478cec0ed4fa2528982cf34483094e9cbc9216e7aa349691242576d552a2a56aaeae426c5303ded677ce455ba1acd9d@13.84.180.240:30303"

The testnet should have synced in 15-20 minutes (from what I read in a couple places) but I have been running for almost 18 hours. There is no error and not struck at any point.

When I tried eth.syncing from the geth console, This is what I got

{
  currentBlock: 1588913,
  highestBlock: 1589055,
  knownStates: 9029253,
  pulledStates: 9020460,
  startingBlock: 1588426
}

I thought I was almost there at the highest block. But this has been the situation for couple of hours. The known states and pulled states are ever expanding.

Is there any other alternative way to download the testnet chaindata which will make the process much faster than syncing it through the geth command?

Best Answer

The reason testnet is taking that long to sync is that you probably have lower than average connectivity. I would use metamask and generate an address on the testnet there. Then I would then deploy the contract on that address. If you are using Remix, you can select the option to inject web3js and it will pick up the meta mask address. If you need some ether to get you going, you can use the Rinkby Faucet that will give you up to 18.75 ETH to play with

Related Topic