Hydra chain-observer adds version detection for a single multi-version binary.

What changed.

A merged Hydra pull request makes hydra-chain-observer version-aware. Instead of being compiled for one Hydra version, the observer checks head and deposit validator script hashes against an embedded registry to identify the relevant version.

The supplied record says one binary now covers Hydra versions 0.13.0 through 2.2.0. For hydra-explorer and teams indexing Hydra heads, that can replace a per-version observer setup with one observer per network.

Why it matters.

The practical benefit is operational simplicity. The record estimates that an explorer backend can reduce its observer count from about 15 processes per network to one, which may reduce the amount of version-specific process management required by operators.

This is a tooling and observation change, rather than a change to Hydra’s consensus, head safety, or throughput. It should therefore be read as an infrastructure improvement for observing supported Hydra versions, not as a new scaling or security capability.

What to watch next.

The next useful receipt is evidence of hydra-explorer or another Hydra-head indexing deployment using the multi-version observer across the stated version range. That would show how the merged change performs in an operator-facing environment.