Cardano Leios Review Shows Real Certificates, Mempool Work and Musashi Dojo Testing

Cardano’s Leios development moved into a more practical testing phase in June, with the team outlining work on certificate aggregation, Dijkstra era block structure, testnet operations, explorer tooling and adversarial testing. Leios is Cardano’s throughput upgrade designed to add endorser blocks to the consensus pipeline, allowing more transaction data to move through the network while keeping security requirements tied to validation, voting and certification.

Cardano Leios Adds Real Voting Certificates

The June review showed progress on the voting and certification workflow behind Leios endorser blocks. The current public testnet already runs basic voting, while the next layer of work adds proper cryptographic certificates, vote aggregation and certificate verification when blocks are applied.

The team described a Leios certificate inside a Dijkstra era block body, moving the implementation beyond placeholder behavior. A typical certificate was described as about 180 bytes for roughly 1,000 voters, with the aggregated signature using BLS cryptography. The demonstration also explained a change in what nodes vote on. Instead of voting only on the endorser block, the implementation now votes on the announcement of that block, because the same endorser block could otherwise be reused across competing chain contexts.

That distinction is part of the security work behind Leios. The protocol is not only introducing larger throughput objects. It must also define how those objects are announced, validated, voted on, certified and attached to the chain. The team said the certificate work is expected to reach the testnet after a respin, because the update changes the block format.

Musashi Dojo Gives Cardano Builders a Live Leios Testnet

Musashi Dojo is now the public test environment for Leios. The official documentation describes it as a testnet and training hall for Ouroboros Leios, where participants can run a node, register a stake pool and begin testing the implementation while the network is still in prototype form.

The review described Musashi Dojo as a long-running integration target for Leios. Its planned phases are Earth, Water, Fire, Wind and Void. Earth focuses on onboarding, basic functionality and correctness. Water is planned for protocol parameter exploration and testing limits. Fire is aimed at heavier network stress, including higher load and real-world latency from globally distributed nodes. Wind is reserved for adversarial testing. Void is framed as final preparation work before a later hard fork path.

The testnet is intentionally not a finished product. It uses pre-release code, can be reset and does not affect mainnet or real ada. That makes it useful for SPOs, dApp teams, explorers, indexers, wallets and SDK maintainers that need to understand how Dijkstra era changes and Leios endorser blocks affect their systems.

Mempool Bottlenecks and Red-Team Testing Shape the Next Leios Phase

The review also focused on the mempool as one of the main engineering constraints for higher throughput. The team said Leios needs a larger and more capable mempool to issue big endorser blocks, while the current Haskell node mempool was designed for Praos rather than Leios throughput targets.

The discussion identified two pressure points. Transaction submission becomes more contested when many peers offer transactions at the same time. At the same time, the node must keep transactions applicable to the currently selected chain while chain selection and block forging continue. The team discussed possible approaches including less blocking mempool behavior, earlier preparation for block issuing and a secondary mempool based on the ledger state expected for block production.

The testing program also includes adversarial nodes. The red-team section described software built to connect to the network and test failure cases under controlled conditions. One early issue involved invalid endorser block data being reflected back to relays, which helped expose and fix a weakness in the prototype. The team is now structuring this tooling so attack behavior can be coordinated across multiple nodes.

That gives Musashi Dojo a specific role in Cardano’s Leios roadmap. It is now a place where certificate behavior, mempool design, downstream tooling, explorer visibility, node diversity and adversarial conditions can be tested against a running public prototype. The practical change is that Leios development is no longer visible only through roadmap language or isolated demos. It is now producing node behavior, testnet blocks, explorer data and reproducible failure cases that can be used before production code is prepared.