Cardano Test Scripts Add Ledger Support for Batch DRep Voting

Martin Lang of ATADA has prepared an update to StakePool Operator Scripts that allows Ledger-backed DReps to sign votes on multiple Cardano governance actions. Highlighted in the Cardano Foundation’s September 2 Community Digest, the update also expands payment options for DRep operations and hardware-wallet support for pool registration. The changes were introduced in the testnet directory.

Batch Voting for Ledger-Backed DReps

The update introduces an “unrestricted” signing mode that supports votes on multiple governance actions using a DRep key held on a Ledger device.

DReps represent ADA holders who delegate voting power to them. Batch signing lets them handle several governance votes together rather than preparing a separate signing workflow for each action.

The feature forms part of compatibility work for the upcoming LedgerApp v8, alongside HW-CLI 1.20 and Cardano-Signer v1.35.

More Flexible DRep and Pool Operations

StakePool Operator Scripts is an open-source command-line toolkit for managing Cardano stake pools, governance operations and transactions. It supports ADA and native-token transfers, hardware wallets, and online and offline workflows.

The update broadens how DRep registration and retirement transactions can be funded. A Ledger DRep key can be paired with funds from a CLI wallet, while DRep operations using CLI keys can use Ledger-controlled funds for payment.

For stake pool operators, the changes support registering or updating a pool using both the pool key and payment key stored on a Ledger device.

Clearer Hardware Error Reporting

More detailed hardware error messages extend across over 15 scripts, including reward withdrawals, asset transfers, delegation, and token minting and burning. These changes address the diagnostic information available when a hardware-wallet operation fails.

The repository maintains separate mainnet and testnet directories, with alpha and beta scripts included in the latter. The announced Ledger v8 additions belong to that testing workflow; production users are directed to the mainnet files rather than treating the test package as a general release.