quietnan

Wait, just for my understanding. For our usecase we operate multiple archiving, tracing nodes. Syncing that from scratch again is not an option, it took several months already last time...

One machine on 3.0.1 and one machine on rakita/11758_use_std_rwlock. Both machines fail to keep up these days, despite sufficient hardware resources.

Me too. Both were using 3.0.1 a while ago. Now we switched one of them to rakita/11758_use_std_rwlock to see if that solves our problems. When I say 'multiple archiving and...

> > Me too. Both were using 3.0.1 a while ago. Now we switched one of them to rakita/11758_use_std_rwlock to see if that solves our problems. When I say 'multiple...

Regarding downgrading a database, https://github.com/ordian/open-ethereum-downgrade-db-to-2-5 does not work for 3.0+. See feature request there, issue 1. Any chance of getting some vetted downgrade script? Happy to participate in testing with...

> @edobry https://medium.com/openethereum/vision-for-openethereum-ex-parity-client-eb7b11f6eef8 Please be more explicit on the "We expect to deliver a migration utility" part. Will you or will you not deliver such a migration utility. You are...

Does anybody have experience with hardware requirements during initial sync of bcashsv? It's "[supported](../blob/master/configs/coins/bcashsv.json)", as in there is a config file, but since trezor does not seem to run an...

Also the server certificate is invalid since June 16th (5 days ago). Seems to be no longer maintained. Any chance of bringing it up again?