Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

OpenEthereum 3.1RC1 is available for testing #11881

Open
claberus opened this issue Sep 30, 2020 · 6 comments
Open

OpenEthereum 3.1RC1 is available for testing #11881

claberus opened this issue Sep 30, 2020 · 6 comments

Comments

@claberus
Copy link

claberus commented Sep 30, 2020

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!

@mdben1247
Copy link

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.

@adria0
Copy link

adria0 commented Oct 7, 2020

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
Copy link

Thanks. Are there any benefits to upgrading from 2.5 vs 2.7/3.0?

@adria0
Copy link

adria0 commented Oct 8, 2020

@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.

@localcryptosMichael
Copy link

localcryptosMichael commented Oct 12, 2020

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.

@compojoom
Copy link

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. 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants