Cardano Scaling Tool Hydra Welcomes Significant Update

In this week’s development report, the Cardano (ADA) ecosystem has listed several updates surrounding its recently launched scaling protocol Hydra. This week, the Hydra team launched version 0.12.0 of the Layer-2 scaling solution although it had previously gone live on the mainnet on last month. 

Evolution of Cardano Hydra Head

Cardano developer Sebastian Nagel shared the update on Twitter (now X) a few days ago. According to the summary provided by Nagel, the upgrade is well-compatible with the Cardano Node version 8.1.2 and the Mithril protocol developed by Input Output Global (IOG). The upgrade came with some performance enhancement and Application Programming Interface (API) improvement features.

As such, Hydra will begin to operate new API endpoints and in that way, become more accessible to Web3.0 developers and researchers. The v0.12.0 upgrade also came with some code optimizations to improve Hydra’s on-chain performance and security.

The first time there was an Hydra upgrade, the L2 scaling solution moved from v0.10.0 to v0.11.0 with defined benefits. Markedly, this move made the protocol fully isomorphic to Layer-1 with the addition of timed transaction support and the long-awaited commit from external wallets.

Some weeks ago, the Hydra team worked on upgrading the specification of the protocol to align with recent on-chain changes. This came with a refactoring of the snapshot emission. To improve compiling times and slightly smaller Plutus scripts, the team also updated to GH 9.2.7. 

Mithril Team Works on Clarity

In addition to the weekly development report, a new contributor joined the Hydra team and is very active in operating the Hydra head. So far, this contributor has participated in the meeting of the Intersect open source committee and also prepared the upcoming Hydra masterclass for an educational initiative for the community known as RareEvo.

Mithril team, on the other hand, has been busy performing cleanup tasks to boost the clarity and reduce the verbosity of the logs and aggregator nodes. Plus, they also made it easy to verify the registration status of a signer by streamlining the processes.