Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internal Yes, correct behavior. false means that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain up to date. Check eth.blockNumber against a block explorer if you want to double-check.
EDIT: web3.eth.isSyncing() will also return false when syncing has not yet started (or is currently not running). If this is the case, you need to check your networking that you are connecting to peers: Why doesn't my Ethereum node have any peers?
Yes, correct behavior. false means that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain up to date. Check eth.blockNumber against a block explorer if you want to double-check.
Yes, correct behavior. false means that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain up to date. Check eth.blockNumber against a block explorer if you want to double-check.
EDIT: web3.eth.isSyncing() will also return false when syncing has not yet started (or is currently not running). If this is the case, you need to check your networking that you are connecting to peers: Why doesn't my Ethereum node have any peers?
Yes, correct behavior. false means that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain syncedup to date. Check eth.blockNumber against a block explorer if you are skepticalwant to double-check.
Yes, correct behavior. false means that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain synced. Check eth.blockNumber against a block explorer if you are skeptical.
Yes, correct behavior. false means that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain up to date. Check eth.blockNumber against a block explorer if you want to double-check.
