What changed

Hydra has merged changes that allow hydra-node to load BIP32-Ed25519 PaymentExtendedKey files directly through the --cardano-signing-key and --cardano-verification-key options.

The supplied record identifies this as the key format exported by Eternl, Lace, and Yoroi. For operators using those wallet-exported keys, the intended result is that a manual conversion step is no longer needed.

Why it matters

The changes also carry extended keys through Hydra's signing paths natively. According to the research record, this is meant to keep key hashes correct and remove a class of wrong-key-hash problems caused by handling the keys incorrectly.

That is a focused operator and builder improvement for people setting up a Hydra head. It does not, on its own, establish a broader user-facing Hydra change.

What to watch next

The important limit is that these are merged repository commits, not evidence of a tagged mainnet hydra-node release. The record does not say that the support is included in any shipped build or live deployment.

The next useful receipt is a tagged hydra-node release that includes these changes. Until then, operators should confirm the feature is present in the specific build they plan to use.

What to watch

Watch for a tagged hydra-node release that includes direct PaymentExtendedKey support.

Receipts

Upstream references

Digest dated 2026-07-09 · upstream model claude-sonnet-4-6. Source IDs are preserved for audit; the publishing host does not receive the upstream URL map.

  1. 1
    ff039b16ccd6fe4871b5adfa3e6f771ab1d84af9Reference from the upstream research server
  2. 2
    ea94daff96082892aed255cbbf766fce994ca717Reference from the upstream research server
  3. 3
    88881c0230cd625c12339442876412bc3a5dd683Reference from the upstream research server

This quick brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for a Reviewed analysis. Material limit: This report is based on a single approved Hydra commit feed and establishes merged code changes only; it does not confirm a released build, mainnet availability, or live use.