Cardano's Scaling Protocol Hydra's Developer Reveals Progress

Last year, Cardano introduced its Hydra protocol, which it has been working on ever since.

Cardano's Scaling Protocol Hydra's Developer Reveals Progress
Cardano Hydra Protocol | Image: Optimisus

The project has been making gains in establishing that it is a force to be reckoned with in the space since gaining smart contract functionality in 2021.

Its decentralized finance (DeFi) sector is gaining traction. It now provides information about the Hydra protocol and how far the team has progressed in scaling it.

Hydra Has Progressed

The developer behind Cardano, known as IOHK, has released additional details on what the project Hydra is up to in a recently published article on its official website.

It describes where the protocol is now, even if it's a long way from where it started.

Hydra, which was developed by the Ouborous team to boost throughput, reduce latency, and deliver cost-effective solutions without losing storage, is still evolving.

Hydra has evolved into a proof-of-concept protocol, which was not part of the original plan. As a result, the project has been pushed toward "a more specified implementation for the testate MVP."

There are various Hydra Heads, each of which has a powerful network layer between Cardano and other blockchains, as well as additional smart contracts that will drive a Hydra Head's lifecycle.

It functions as a mini-ledger, identical to the Cardano network's on-chain main ledger but on a smaller size, as well as off-chain.

With this protocol's consensus method, all parties involved in a transaction must agree before the transaction can proceed.

Cardano going to a million TPS

The Cardano network's ability to perform a large number of transactions per second is one of its selling factors. But that isn't all there is to Hydra.

Although TPS may appear to be an essential statistic, the paper concludes that it is the least useful indicator to use when comparing transactions because they might be of various shapes and sizes.

Instead of TPS, the paper recommends focusing on throughput, finality, and concurrency, as these metrics are more significant in the big picture.