Application Status
Status: Active
Hey everyone,
We’re back with another quick roundup, below is a summary of what’s been happening across the team over the past two weeks.
Weeks 16–17 (April 15 – April 28, 2025)
Mihail Dobrev
We debugged an issue where some AEX-9 tokens were incorrectly invalidated due to a negative balance, even though the balance was zero. After investigating a potential race condition in AEX-9 token record creation, we confirmed it wasn’t the cause (MDW simply cannot track balances when the contract is initialized with a starting balance).
To improve handling of these cases, MDW now flags invalid AEX-9 contracts with a reason instead of just throwing an error.
We also began writing a migration to index the count of all account activities and ran the account counts migration on testnet.
Additional fixes included resolving an out-of-memory crash during migration and lowering the log level for async transaction stat mutations to reduce log noise. We also updated the Swagger docs PR to address outstanding feedback.
Justin Mitchell
This cycle focused on discussions and reviews to support ongoing development.
Hans Svensson
We assisted with troubleshooting AEX-9 contract balances with MDW, Aescan, and the token bridge. Documentation was added for recent changes to FATE operations for HyperChains.
As the project nears its close, we’ve been wrapping up loose ends with ongoing meetings and documentation efforts. Additionally, we helped Måns conceptualize and begin coding a mechanism for Proof-of-Fraud that bypasses traditional PoW logic—an important step for HyperChains.
Richard Carlsson
We’ve been exploring options for caching in contracts to improve performance. Additionally, we contributed to discussions around Proof-of-Fraud handling and made another attempt at resolving the ongoing logging issue.
Måns af Klercker
We continued development on the penalties feature, while also taking part in discussions around Proof-of-Fraud functionality for PoW chains.
Dincho Todorov
We focused on infrastructure fixes following cost optimizations and system tuning. This included respawning the HyperChains demo network and deploying the aepp-hyperchain-bridge.
Thanks for following along—feel free to share your thoughts or questions with us anytime!