The Minerva hard fork was activated last Thursday (07.03.2019) migrating all Phase 1 AE tokens and introducing a number of consensus-breaking improvements. You can look at the release notes for a detailed list of changes. We are happy to announce that:
The first scheduled protocol upgrade of the æternity protocol was performed without any issues. It was one of the smoothest hard forks in the industry.
The dev team continues to closely monitor the stability of the network. So far no deterioration of the network stability has been detected.
The team also announced the second Minerva Release 2.1.0 that includes fixes to the Windows package that were previously included in a Windows-only hot fix 2.0.1, expands the æternity node API and introduces a number of improvements to the State Channels’ Finite State Machine (aka FSM).
The 2.1.0 release:
- fixes the build of Windows package,
- includes the new Minerva accounts file,
- uses proper data directory,
- fixes the
syncingfield in the
- adds a
sync_progressfield to the
/statusexternal endpoint (
sync_progressmetric is now also reported every 30 seconds during the sync process).
- exposes logged events (as a
logfield) in ContractCallObject in the HTTP API,
- improves the stability of State Channels’ FSM,
- adds a new WebSocket method for dry-running off-chain contracts:
In the following weeks the developers will focus on finalizing æternity’s Stratum protocol implementation, improving and extending the VM, and enhancing the functionality of State Channels.
æternity’s development topics are now better organized in the Forum and you are all welcome to join the discussions there.
Interested in æternity? Get in touch: