This month, our development efforts were focused on refining and stabilizing the Lithium protocol, bringing it closer to an auditable state and, ultimately, mainnet readiness. These upgrades are the result of continuous testing — with many of you in the community actively contributing. Thank you!

This cycle introduced new functionality while further optimizing existing features to enhance stability and efficiency.

One of the key additions is a new mechanism to revoke channel states. During testing, we identified rare cases where channels could become “stuck” due to mismatches between a user’s local state and the network’s perceived state. Such situations can occur, for example, if a user loses connection right as a channel update (sending, receiving, opening, or closing) takes place.

The new revocation mechanism prevents this by allowing outdated states to be safely invalidated, ensuring smoother recovery and overall robustness.

We’ve also added support for batch operations, allowing multiple on-chain actions — such as funding, withdrawing, opening, or closing channels — to be executed within a single transaction. This significantly reduces gas usage and streamlines operations.

For hub operators, this means it’s now possible to process several users’ requests simultaneously (e.g., multiple channel closures). For Hydranet users, it will later enable combined operations like depositing and renting liquidity in one transaction — improving both efficiency and user experience.

As a reminder, Lithium consists of two components:

• an on-chain contract, and
• an off-chain protocol defining off-chain interactions.

Both have been updated to support the new functionality. Additionally, the on-chain contract has been size-optimized to facilitate smoother on-chain deployment.

The updated version of Lithium has already passed internal testing and is expected to be deployed for public testing in the coming weeks.

Lithium has indeed been one of our main areas of focus this past month, alongside the usual updates aimed at resolving various bugs and edge cases. To close out this monthly recap, we would also like to address a recent change within the team.

Hans, our former Marketing Lead, has stepped away from the project and no longer holds any ongoing responsibilities or presence within the team. His skill set did not align with the project’s updated needs, though he remains available for contracted work on an as-needed basis.

We are pleased to share that Mito has now taken on the role of Marketing Lead. He has already been working closely with the development team to shape and execute Hydranet’s growth strategy, with a clear focus on attracting and retaining users as we move toward mainnet.

‍