Crypto²

1. This would be the expected behavior but in these cases I'm seeing it will start without printing any errors and with a new seed. It mainly happens if there...

It's only up to 2245276 right now.

No it's still way behind. For example I'm only on block 2248073 now and current on wavesexplorer is 2249822 so still over 24 hours behind even after running 11 days.

It's on the right chain, it's just syncing extremely slowly. Normally I keep the log off, I turned it on now and will post one later on.

Not well, I've also tried it on a dedicated server with a lot more power as well and it's a bit faster but still crawling. I don't see any errors...

It has caught up now. 25 days to sync is pretty crazy :(

It is definitely still slow, I updated to the latest about 24 hours ago since I was having rollback issues and saw there was an update. It was only 2000...

Def still an issue in version 1.3.6. I had to move Waves to a new server and downloaded the latest snapshot and it's as slow as ever syncing up from...

I'm not generating millions/day, I said that's how long it takes to restore a wallet if it crashes/corrupts and you have to restore from seed and you had a bunch...

PHP, this is over the RPC to the internal wallet. Individual addresses are fast, it's just when you have thousands+ of them it adds up to a lot of time....