Overview
Cardano Scaling is an engineering group whose open-source projects let developers move funds and verify chain data faster and more cheaply1. It brings five of them under one banner: Hydra, Mithril, ALBA, Peras, and Leios, each aimed at a different bottleneck1. The group kept a monthly progress report through October 2025, and the archive links what shipped to the code behind it2.
Much of this work runs inside Input Output, the company that develops Cardano's core software; Leios, for one, describes itself as an Input Output research project3. Cardano Scaling is a coordinating banner rather than a company, and its own site notes the group is still settling which repositories and communication channels belong under its name1.
Key Features
- Payments that settle without waiting for a block. Hydra is a layer two, a side network where a small group of participants exchange funds among themselves off the main chain and report only the final result back to it4.
- Familiar tools carry over. Hydra uses the same transaction format and ledger rules as the main Cardano chain, so wallets, DApps, and developer libraries written for the chain need little rework to run against a Hydra session4.
- Start up without downloading the whole chain. Mithril has stake pool operators jointly sign snapshots of the blockchain, so a wallet, exchange, or light client can trust chain data by checking one signature instead of replaying the history itself5.
- A crowd of signatures compressed into one. ALBA is a cryptographic technique that lets someone prove they hold a large set of items, such as votes or signatures, by revealing only a small sample of it6.
- Research pointed at the base layer. Peras works on how long the network waits before treating a transaction as settled for good7, and Leios works on how many transactions the chain can carry at once3. Both change Cardano's consensus rules, the method the network uses to agree on a shared history.
What to Expect
The Cardano Scaling site is a signpost rather than a destination: a short statement of purpose, the project list, and an archive of monthly reports1. Each report walks through what changed in Hydra and Mithril and links out to the issues and pull requests behind it, so the claims are checkable against the code2.
Developers get the most out of it. Hydra, Mithril, Peras, and Leios each keep a separate documentation site with protocol explanations, and Hydra and Mithril add tutorials for running them; the source code sits in public repositories on GitHub458. Stake pool operators have a direct role too, since Mithril depends on operators running a signer alongside their pool5.
For questions, the group points people at the Input Output technical community server on Discord, where dedicated channels handle Hydra and Mithril1. Each monthly report doubled as an open review meeting announced in that chat, with slides and a recording published afterwards2.
