Hydra adds a separate deposit-activation setting

What happened

Hydra has added a `--deposit-activation SECONDS` local-node configuration flag. It controls when a deposit moves from the Inactive state to the Active state.

The setting separates a deposit lifecycle into maturity, active, and recovery windows. Under the default value of 3,600 seconds, behaviour remains byte-identical to the previous implementation.

Why it matters

Hydra head operators and integrators can tune deposit activation independently from the deposit deadline without changing a HeadParameter or making a protocol change. That makes the setting an opt-in operability adjustment for deployments that need different timing control.

For operators with no need to change deposit timing, the stated default means there is no required behaviour change. The update sits within a dev-heavy scaling feed, where Hydra and Leios work dominated the available records.

What to watch next

The practical receipt is adoption in Hydra local-node configurations and any follow-up implementation or operator documentation showing how deployments use separate maturity, active, and recovery windows. This record does not establish how widely the option will be used or its effect in live deployments.