-
Notifications
You must be signed in to change notification settings - Fork 1.7k
OpenEthereum 3.1RC1 is available for testing #11881
Comments
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 |
Thanks. Are there any benefits to upgrading from 2.5 vs 2.7/3.0? |
@mdben1247 |
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. |
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!
The text was updated successfully, but these errors were encountered: