Hydranet, we continue to push forward. March has been another month of steady progress as we continue moving Hydranet closer to mainnet. The progress includes the Lithium audit process, platform performance and overall infrastructure reliability.

The Lithium audit

The Lithium audit is still underway, and we are steadily progressing into its final stages, working to complete it as quickly as possible.

As mentioned in our previous recap, addressing the reported findings is not simply a matter of adjusting a few lines in the contract. Each change must be evaluated with the remaining infrastructure to ensure it does not introduce unintended issues elsewhere in the system.

To achieve this, every fix is deployed and tested within the full infrastructure. With automated testing and trading bots we can quickly identify any faulty behaviour and find a resolution for it.

So far, the results are promising, and the system continues to perform as expected. We can’t wait to share it with our testers!

Other infrastructure and stability improvements

Alongside the audit process, we’ve continued strengthening the overall infrastructure and its reliability. This includes improvements to pricing data handlers (so called price oracles), to provide more accurate and reliable swap executions, improvements to the channel rental manager by introducing functions that will improve the user experience, better gas cost estimations for on-chain interactions, and more.

These changes are not always visible on the surface, but make a huge difference for the overall user experience.

Swap success rate

Speaking of stability, one question that often comes up is the swap success rate. There are several factors that influence the swap success rate, including order book conditions, the swap engine itself, user connectivity, and payment resolution across different networks. Naturally, achieving a perfect success rate in all situations is challenging. But is it impossible?

Recent observations have been very encouraging. During the latest rounds of automated testing using trading bots, no failures have occurred due to the order book, swap engine, or payment resolution. When swaps have failed, the cause has been exclusively related to connectivity issues. In cases where no such issues were present, the bots have continued running without interruption until manually stopped.

Dare we say 100%? In a world with perfect connectivity, it does indeed look like it.

For those keeping an eye on the stats dashboard at https://stats.hydranet.ai/, the recent activity likely hasn’t gone unnoticed. We hope to open this up for broader participation soon! But until then, please give it up for our trading bots.