Important Notes about v2.0.0 Upgrading Timeline
As we see at the mid-of-July hardfork plan, the official
v2.0.0 release binaries will be ready at 1st July.
And as you already know, in this hardfork release, there’s a designed incompatibility between
v1.x.y wallet and
v2.0.0 wallet. (for detail, refer to addressing recent transaction difficulties), please understand this incompatibility behavior and it’s already been heavily discussed and settled down.
v2.0.0 binaries has been released at 1st July, I want to remind that ALL the users / pools / exchanges should upgrade to this
v2.0.0 ASAP, to avoid the Wallet Incompatibility between old version (
v1.x.y) and this new version
Especially for Pools / Exchanges.
It’s definitely not good for the users of these pools / exchanges if confused about what exact the wallet version they should use! And also it’s boring for pools / exchanges if got too many failure reports for user when deposit / withdraw the Grin, just because of the incompatible version.
To be simple, after
1st July, any good Grin wallet should be at version
v2.0.0 (or later version if have).
I want to highlight this v2.0.0 Upgrading Timeline, since now just
5 days before the official
v2.0.0 release and this global upgrading.
For Pools / Exchanges
Lock both the Grin deposit and withdraw at the day of upgrading (1st July proposed), and upgrade the production environment’s Grin Servers and Wallets to
v2.0.0, and the necessary test of course.
After the upgrading, show an explicit reminding message before user start to deposit or withdraw, ask user upgrading their Grin Wallet to version
v2.0.0(or higher version if have), otherwise any deposit or withdraw will just fail.
For All Users
Upgrading Grin wallet to
1st July, to avoid any incompatible failure with Pools / Exchanges 's Grin wallet.
For Grin Community Wallet Developers
To be inline with this upgrading timeline, release corresponding
v2 wallet version at same date (
1st July). Or if can’t catch up this date, at least write a reminding message on their old binaries to tell users NOT use those old versions any more.