What happened

Hydra PR #2800 has merged to master and changes the hydra-tui commit-key option from --cardano-signing-key to --funds-signing-key. The change also updates the internal field, help text, demo, and documentation.

The stated purpose is to disambiguate two key roles in a Hydra head. The fuel key is the internal wallet, while the funds key is associated with the UTxO being committed. The previous hydra-tui option name could blur that distinction.

Why it matters

Operators and integrators that script Hydra head commits through hydra-tui will need to replace the old flag before upgrading to code that includes this merge. The record characterizes the rename as breaking, so an unchanged script may no longer match the updated command-line interface.

The narrower naming may also make key handling easier to read in operator workflows by identifying the key used for committed funds separately from the fuel key. This is a developer-facing maintenance change, not a new user-facing feature.

What did not change

The scope is limited to hydra-tui. Hydra-node’s own --cardano-signing-key and --cardano-verification-key options are explicitly unchanged, as are the related YAML configuration keys.

The merge is a commit on Hydra’s development repository. The supplied record does not present it as a tagged release, a mainnet change, or a hardfork. Feed notes also describe the day as development-only activity from primary developer feeds, without press corroboration.

What to watch

Watch the next Hydra upgrade or release materials for whether they include PR #2800, then confirm that affected hydra-tui commit scripts use --funds-signing-key.

Sources and limits

Upstream references and independent checks

Digest dated 2026-08-22 · upstream model claude-sonnet-4-6. Direct links are matched to all 1 upstream source IDs.

  1. 1
    Unify docs key naming to fuel and funds (#2800)Direct upstream source · c9ead4b2d1948dade144a00b9ac643928bedfb35

This Research brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: This brief relies on one approved primary development-feed record for a merged master-branch change; it is not corroborated by a tagged release, mainnet event, or news-lane reporting.