I assume the developer needs the fresh bootstrap to revive the explorer.
Mine is still syncing... slowly
. Its at Oct 10 2019 currently, block 2020520. I assume it will finish somewhere in March, in the best case.
As i understand on site in this messageMine is still syncing... slowly
. Its at Oct 10 2019 currently, block 2020520. I assume it will finish somewhere in March, in the best case.https://bitcointalk.org/index.php?topic=1028119.msg51578743#msg51578743
have blockchain for 25.01.2020
But i don`t know now much block in him
Yep, thanks. I am syncing from scratch though. Not sure it was necessary, but just as an experiment (probably wouldn't do that if I knew it will take so long). 8-bit is somewhat prone to forks, I will check the blockhash as soon as I sync to that date. I bit of patience - I assume in two-three weeks the sync will complete
. Most probably there are folks with fresh chain, but they are silent.Maybe another node stuck because they use 32 bit client?
I use the Linux client natively compiled on my Linux VPS. It is 64-bit machine, so yes, my client is 64-bit.
I assume most (if not all) clients are 64-bit now, as its hard to find 32-bit machine now, and most people have no reason to use 32-bit OS on 64-bit system, or specifically compile 32-bit daemon on 64-bit OS.