parity-ethereum
parity-ethereum copied to clipboard
openethereum
OpenEthereum 3.1RC1 is available for testing
Our new release candidate OpenEthereum 3.1RC1 is available for testing.
3.1rc1 is a candidate release based on v2.5.13 which is the last stable version known of the client that does not include any of the issues introduced in v2.7. It removes non core features like Ethereum Classic, Private Transactions, Light Client, Updater, IPFS and Swarm support, currently deprecated flags such as expanse, kotti, mordor testnets.
https://github.com/openethereum/backport-3.1/releases/tag/v3.1.0-rc.1
The database migration tool is for testing purposes only, not ready for production.
We need your support to test it. Any feedback is very appreciated!
Just to clarify. Is database migration needed also for 2.5.13 databases? Recommendation in #11858 seems to imply 3.1 will work with 2.5.13 db without upgrading, however that doesn't seem to be the case. Running 3.1RC1 asks to run the migration tool.
Just to clarify. Is database migration needed also for 2.5.13 databases? Recommendation in #11858 seems to imply 3.1 will work with 2.5.13 db without upgrading, however that doesn't seem to be the case. Running 3.1RC1 asks to run the migration tool.
Yes, the database migration is also required for 2.5.13
@mdben1247 3.1 is a backport of 2.5.13 and shares the same internal rocksdb version, so you are not going to have any problem migrating the database. 2.7/3.0 uses a diferent rocksdb version (a never one), so we cannot guarantee if there is going to be any additional data corruption over the time.
We need your support to test it. Any feedback is very appreciated!
We successfully migrated a 3.0.1 archive +tracing node to 3.1RC1. Running without issue so far.
We managed to migrate parity 2.3.6 database with the db-upgrade-tool and then to successfully start the openethereum client. It's now working for a couple of hours and it looks good. 👍
