Amaru Open Mainnet Block Forging for Cardano Rust Node

PRAGMA latest beta release introduce mainnet block production capabilities, mempool transaction selection, and CIP-0203 software identification for Cardano alternative node implementation.

By SongMarketCap

Updated:

Cardano News - Amaru Open Mainnet Block Forging for Cardano Rust Node

PRAGMA don announce Amaru v10.11.20261105, one beta release wey dem design to enable block forging for Cardano mainnet using im Rust-based node implementation. The update remove the previous restriction wey bin limit block production to test networks and introduce functionality wey go allow stake pool operators produce blocks without to depend on the reference Haskell node.

The release push Amaru Minimum Viable Block Producer milestone forward, extend im existing capabilities pass blockchain synchronization, validation, and relay operations.

Amaru Expand Block Production Reach Cardano Mainnet

PRAGMA dey maintain Amaru, wey be independent implementation of the Cardano node wey dem write for Rust. E implement networking, ledger validation, and consensus functionality separate from the reference Haskell software, provide alternative codebase to operate inside the Cardano network.

Before this update, Amaru fit already function as mainnet relay, synchronize through Mithril snapshots, validate incoming blocks, and follow the blockchain current state. But im block production capabilities still remain limited to test environments. The new release remove that restriction and add transaction selection from the mempool, where pending transactions dey before dem include dem inside blocks.

Dem go consider transactions based on the order wey dem take arrive, and any wey pass the permitted block size or execution limits dem go skip am during construction. The update also introduce CIP-0203 software identification, wey allow blocks carry information about the node implementation wey produce dem.

Software tagging dey enabled by default. Operators fit disable am with the --software-tag-off option or the AMARU_SOFTWARE_TAG_OFF=true environment variable, while the new amaru dev software-tag command provide tools to inspect and decode the identifiers.

Ledger Corrections and Operational Improvements for Stake Pool Operators

Beyond block production, the release include corrections wey aim to improve consistency with Cardano reference implementation. These ones address calculations wey dem dey use to determine block producer eligibility, including rounding edge cases, plus discrepancies for transaction validation wey involve collateral returns, witnesses, governance operations, and failed Plutus script execution.

Monitoring capabilities don also expand. Additional connection metrics support tools like gLiveView, and Key Evolving Signature (KES) metrics don align with the ones wey the Haskell node dey expose. These changes dey provide operators with more consistent information when dem dey monitor node connectivity and block production infrastructure.

According to the release documentation, Amaru require x86_64 or aarch64 processor with at least two cores wey dey run for 2 GHz, minimum of 2 GiB of RAM, and between 20 and 300 GiB of storage. The storage amount depend on the blockchain history wey the operator synchronize.

Amaru no dey automatically retrieve the entire chain history during initial bootstrapping. Operators fit synchronize additional history separately through amaru mithril sync. The default port for incoming peer connections na 3001 instead of 3000, and configuration options dey available for operators.

[NEWSBREAK]

Mainnet Deployment and Software Identification

Intersect Hard Fork Working Group identify November 5 as the target date for Amaru to begin produce blocks for Cardano mainnet. PRAGMA release documentation describe the functionality wey needed for that milestone, although the release information no identify specific mainnet block wey Amaru don successfully produce.

The beta software dey available for Linux on x86_64 and aarch64 architectures, macOS on aarch64, and Windows. Dem also specify Docker image under ghcr.io/pragma-org/amaru:v10.11.20261105.

The change concern stake pool infrastructure, no be how ADA holders dey interact with the network. Wallet functionality, delegation, and staking participation remain unchanged no matter which node implementation the pool dey operate.

CIP-0203 provide mechanism to identify the software wey dem use take produce individual blocks. When Amaru-generated blocks wey carry those identifiers appear for Cardano mainnet, people fit distinguish their origin from blocks wey the reference Haskell implementation produce.