Amaru Fixes Sync Failures in Cardano Node Beta

Amaru released a beta on September 25 that fixes an epoch-boundary synchronization failure and a crash involving complex smart contract code.

Developed under PRAGMA, Amaru is an independent implementation of the Cardano node. The update strengthens the relay software that operators can test today.

Beta Addresses Two Node Failures

Version v10.11.20260925 fixes a case in which expired governance proposals left related records behind. Those records could stop the node from synchronizing at the next epoch boundary.

The release also prevents deeply nested UPLC programs and constants from causing a stack overflow during processing. UPLC is part of Cardano’s smart contract execution system, so the fix addresses how the node handles that code.

Operators now receive clearer errors for invalid configurations, incompatible storage versions, and inconsistencies between ledger and chain data.

Applications that embed Amaru can also detect when the node has shut down and inspect failures in its components. Together, these changes make a stalled or crashed relay easier to diagnose.

What Amaru Adds to Cardano Infrastructure

Amaru is an open-source node client written in Rust. Operators and developers can run it to follow and relay Cardano data, then inspect its behavior through logs, metrics, and traces. It provides a separate codebase alongside the existing Haskell node.

That distinction matters even on a network with many independently operated stake pools. If most pools use the same implementation, a defect in that software can affect many of them at once. A second client can reduce this shared exposure as it becomes reliable and gains adoption.

Both implementations must agree on Cardano’s rules, from validating transfers of ADA to calculating staking rewards in ADA. Amaru uses conformance tests against the Haskell node, deterministic simulations, and property-based testing to examine that agreement. Independent code is useful to the network only when it processes the same data consistently.

The current beta lists a minimum of 2 GiB of memory and supports x86_64 and aarch64 systems. These are existing project requirements, not a hardware reduction introduced in September. Amaru also uses Mithril when preparing snapshots that help operators start a node without processing the entire chain from its beginning.

Relay Testing Comes Before Block Production

At September’s Cardano Ambassador call, Amaru was described as a relay beta. An alpha capable of producing blocks was presented as a target for October or the fourth quarter, and the related GitHub milestone remains open.

The team is scheduled to discuss its progress at Cardano Node Diversity Celebration Day in Singapore on October 6, with an online broadcast. The event will also introduce a participation program for operators. The approach outlined at the Ambassador call includes registering a stake pool, running Amaru with evidence of operation, and reporting bugs or contributing features. Incentive details have yet to be announced.

The September release gives those operators a clearer test of Amaru’s present role: whether an independent Rust relay stays synchronized across epoch transitions, handles complex UPLC inputs, and reports failures clearly. Producing Cardano blocks remains a separate, open milestone.