It has been some time since the original The Road to Lima post has been published and while it holds still tue, now there are actual dates!
With PR2830 on the node repository we have now two dates for the HF for testnet and mainnet, that would be
- Wednesday the 16th of October 2019 for Testnet
- Wednesday the 30th of October 2019 for Mainnet.
v5.0.0 is almost finalized (rc3 was released yesterday and it looks like no further changes will be needed to became the final release). And the compatible SDKs will be released shortly with support for both Fortuna and Lima protocols and releases.
The new compiler version
v4.0.0 is also almost here, with the
v4.0.0-rc5 looking promising.
In terms of the API Gateways, the proposed timeline is the following for Testnet:
- Thursday 10/10 -> node update to v5.0.0(-rc3)
- Wednesday 16/10 -> Lima HF
That means that if you reference the API Gateway you will have to update your application befor Thursday the 10th.
For the API Gateway on Mainnet
- Wednesday 16/10 -> node update to v5.0.0
- Wednesday 30/10 -> Lima HF
That means that you will have 2 additional weeks to make sure that your application works with the Lima version.
The nodes behind the Middelware (Aeternal) will follow the same timeline.
For the hosted compiler the default compiler will remain the same (3.2.0) until the Mainnet HF, but the latest version is available at latest.compiler.aepps.com and that is the one it will be required after Lima HF, but more on this later.
So this is a good time to focus on what is changed for the SDKs users and what you should be careful about:
Aens: after the Lima HF it will not be possible to claim names with
.test tld, only
.aet will be allowed. At the same time, names less then 13 characters long will enter in the auction phase before being successfully claimed (here the documentation, and here the presentation from @michalzee at the aeunvierse conference)
Contracts: it is required to use the compiler
v4.x.x after lima HF, the output from the compilers version
< v4.0.0 is not accepted by the node. Also, Lima introduces a new and improved VM: FATE (here the FATE specifications and here the talk by @Happi), if you use the SDKs that will be the default vm that is going to be used when compiling/encoding/decoding, that is: FATE is the default VM for the SDKs. If you need to interact with contracts that are already deployed and run with the AEVM than you will have to instruct the compiler client to use the backend
AEVM. This applies to generalized account as well.
State Channels: state channel support functionalities are not up to date with the latest improvements and it will be the focus of the next releases iteration.
Follow the aeternityTECH to stay up to date with the SDKs releases.