Dear Ambrosus community and masternode operators,
The Ambrosus team is excited to announce another sequence of technical updates on the Ambrosus Network. Today, the technical blog features an initial selection of the updates and deliverables in accordance with the roadmap published earlier in July 2020. Q3 has almost come to an end, which means the technical team has a list of deliverables to present to you in this overview of updates.
With the release of this blog, the deployment of status.ambrosus.сom is imminent! Status.ambrosus.com features all services of Ambrosus, including how to become involved in building and running verticals within the ecosystem on one single webpage.
Furthermore, with the latest update, the Parity version (Ambrosus Network is based on Parity AuRa) will now be displayed on stats.ambrosus.com, not to be confused with the aforementioned webpage. This may only happen after all operators update their masternodes. Furthermore, the Hermes masternodes (now free and open-source to deploy), are displayed on stats.ambrosus.com, too. Moreover, two other consecutive Hermes updates (1.1.8 and 1.1.9) now allow for Assets and Events to be linked to the very organization that created them. Before, Assets and Events from Hermes masternodes were all mixed together from a spectator’s perspective. For the Ambrosus Node Onboarding Package (NOP), the Mongo DB version has now been updated to 4.2.9.
Masternode operators who need to export their masternode’s statistics and performance can now do so with the fixed CSV-file export functionality. Bundle information, assets and events are also now displayed accordingly in the bundles, aside from general bug fixes to explorer.ambrosus.com. In addition to that, the order of starting bundle transfers during retirement has now changed. This effectively means the latest exported bundles are transferred first. With this mechanism now in place, it enables the transfer of as many bundles as possible during retirement without interruptions.
Furthermore, it should be noted that the team is currently busy building a standalone application for Ledger support, as the solution originally planned unfortunately did not match the expectations. This more sophisticated solution is going to take more time than was initially taken into account when the roadmap was launched.