[Active] AE Maintenance (Weeks 10-11, 2025)

Application Status

Status: Active

Hey everyone,

Another two weeks, another set of updates! Here’s what’s been happening across the team.

Weeks 10-11 (March 3 - March 16, 2025)


Dincho Todorov

We redeployed HyperChain networks and fixed related infrastructure and scripts to ensure smoother operations. Additionally, improvements to the monitoring platform were made, applying further fixes and enhancements.

Mihail Dobrev

We debugged issues with account stats migration on testnet staging and bumped the node in MDW to RC5, running a new HyperChain to verify its expected behavior. Additionally, we introduced an endpoint to retrieve the top miners for the last 24 hours.

Further efforts included reorganizing HyperChain endpoints into their scope, and refining error messages.

A bug causing MDW to fail when serializing activities for names created by a contract call was fixed, alongside rebasing and [refining the top miners endpoint(feat: top miners for the last actual 24hs by yaboiishere · Pull Request #2111 · aeternity/ae_mdw · GitHub) and refactoring the account stats endpoint. We also reviewed Swagger changes, added correct transaction fields to Swagger specs, and rebased branches after a master rewrite, adjusting the MDW version from 2.0.1 to 1.101.0.

Lastly, we investigated an issue where name claims in auctions appeared in the activities endpoint but not in the name claims one.

Justin Mitchell

We began splitting fork and epoch length into separate votes, improving the flexibility of the voting process (PR). Development on vote splitting was completed, finalizing the changes to enhance decision-making within the protocol (PR).

Hans Svensson

Most of the time was spent troubleshooting and fixing an issue with the latest release. It turned out that in a test setup with a single node and multiple validators running on that node, the voting mechanism failed to complete the protocol.

We had an in-depth review and discussion on Pinning, focusing on when pins should be allowed. We also bumped an old dependency in aesophia_cli and performed overdue maintenance on enoise , as OTP’s crypto library now covers all necessary primitives, eliminating the need for enacl/libsodium .

Thomas Arts

This period was focused on meetings, discussions, and reviews, contributing to ongoing planning and alignment efforts.

Måns af Klercker

We started working on parent pinning height validation. This work was completed and merged this past week.

Jan Michek

We worked on improving server handlers and addressing issues related to confusing scientific notation for numbers in aescan.io. Preparations for the 0.21.0 release are underway, along with enhancements to auction displays and an increase in the statistics limit. Additionally, improvements were made to end-to-end testing to ensure a smoother and more reliable experience.


As always, we appreciate your input, feedback, and ideas. Let us know what you think!

Excuse me, but how long do you think it will be before the official version of Hyperchain is released? There is quite a lot of interest in the community regarding this question. An approximate time frame would be fine, not an exact date.

Hi @AE_UP.

The latest version of Hyperchains is v1.0.0. That’s the first stable release of hyperchains and it is very much official. Everyone interested in Hyperchains should feel free to explore the latest release.

Outside Review
Until there has been an outside review of the Hyperchains consensus protocol, there is still a warning not to put value onto a hyperchain. Though the core team feels v1.0 is stable, it’s good practice to have outside eyes confirm the results of our internal testing. Outside review should commence soon, but it’s not possible to speculate on when that will be complete as it’s not known whether or not issues will be found that need remediation.

Added Functionality
It’s worth noting that the Foundation is supporting developers with grant projects that build on the core functionality of hyperchains in order to make operating hyperchains more practical. For example:

Hyperchain Bridge
@yusufseyrek’s work will allow hyperchain owners to bridge assets created on their hyperchain (for example, the chain’s native token) over to the æternity network. Bridged Hyperchain assets can then be used with aepps like the DEX where it’s possible for them to interact with other assets on AE—including wrapped EVM assets.

Hyperchains Economic Modeling
Configuration parameters for Hyperchains are very complex with layers of dependencies that determine the economic viability of the Hyperchain economy. The core team is currently testing recommendations from the mathematical models constructed by @Sabrina and the data scientists at Noma. These parameters will be part of the web UI for Hyperchains as a guide to ensure HC initiators start with viable configurations and can focus their creativity on their use case.

Hyperchains Web GUI
The web GUI that has largely been built by @keno.chain and @Prime at https://init.hyperchains.ae/ is being extended to include workflows for validators and delegators. While the CLI is unlikely to dissuade the kind of users who initiate a Hyperchain, the GUI will include the configuration parameters mentioned above and also be the entrance point for less technical Hyperchain participants who want to run a validator or just delegate tokens to increase the stake of a validator.

In order for Hyperchains to be a well-rounded product, a lot of moving pieces need to work together on par with all that has been built for the æternity Network. However, the core technology is already available as of v1.0—the additional functionality coming from the grants above are just icing on the cake.

4 Likes

I’m very happy to hear the news. The community is very excited about it. I didn’t expect that the construction of the bridge was also being carried out simultaneously. We look forward to the launch of the superchain and the listing of the first batch of tokens. We will be the first batch of stakers to give it a try :slight_smile:

3 Likes