Why did EOS fail to catch up with the latest block since yesterday? It was always a few minutes behind The latest block that was chased before but now can't be synchronized to the latest block and can't be transferred

  • Please be a bit more specific.
    – TeeAttack42
    Jan 17 '20 at 16:26

EOS is very CPU-intensive. In my case (16 cores, 64G RAM, NVMe SSD, 100mbps internet connection) sync from scratch using history plugin takes about a month.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.